x86-32: use specific __vmalloc_start_set flag in __virt_addr_valid

Browse source

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>

...

This commit is contained in:

Jeremy Fitzhardinge 2009-03-04 16:10:44 -08:00 • committed by Ingo Molnar

parent a964e33c5d

commit dc16ecf7fd

3 changed files with 12 additions and 4 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

5

arch/x86/include/asm/pgtable_32_types.h

View file

4

arch/x86/mm/init_32.c

View file

7

arch/x86/mm/ioremap.c

View file