| commit | dc16ecf7fd1fad7436832121435d4926a81d469e | [log] [tgz] |
|---|---|---|
| author | Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> | Wed Mar 04 16:10:44 2009 -0800 |
| committer | Ingo Molnar <mingo@elte.hu> | Thu Mar 05 14:53:10 2009 +0100 |
| tree | f33060fc5aec6105c624ad660711f87bc8c074c9 | |
| parent | a964e33c5d7c0ea46376d20c2f02edf01c9db251 [diff] |
x86-32: use specific __vmalloc_start_set flag in __virt_addr_valid Rather than relying on the ever-unreliable system_state, add a specific __vmalloc_start_set flag to indicate whether the vmalloc area has meaningful boundaries yet, and use that in x86-32's __phys_addr and __virt_addr_valid. Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>