x86-32: use specific __vmalloc_start_set flag in __virt_addr_valid
commitdc16ecf7fd1fad7436832121435d4926a81d469e
authorJeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Thu, 5 Mar 2009 00:10:44 +0000 (4 16:10 -0800)
committerIngo Molnar <mingo@elte.hu>
Thu, 5 Mar 2009 13:53:10 +0000 (5 14:53 +0100)
treef33060fc5aec6105c624ad660711f87bc8c074c9
parenta964e33c5d7c0ea46376d20c2f02edf01c9db251
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>
arch/x86/include/asm/pgtable_32_types.h
arch/x86/mm/init_32.c
arch/x86/mm/ioremap.c