x86, mm: Fixup code testing if a pfn is direct mapped
authorJacob Shin <jacob.shin@amd.com>
Sat, 17 Nov 2012 03:38:48 +0000 (19:38 -0800)
committerH. Peter Anvin <hpa@linux.intel.com>
Sat, 17 Nov 2012 19:59:09 +0000 (11:59 -0800)
commitdda56e134059b840631fdfd034784056b627c2a6
treef7369202429bc6204b0e5062426982265be0fb46
parent4eea6aa581abfeb2695ebe9f9d4672597e1bdd4b
x86, mm: Fixup code testing if a pfn is direct mapped

Update code that previously assumed pfns [ 0 - max_low_pfn_mapped ) and
[ 4GB - max_pfn_mapped ) were always direct mapped, to now look up
pfn_mapped ranges instead.

-v2: change applying sequence to keep git bisecting working.
     so add dummy pfn_range_is_mapped(). - Yinghai Lu

Signed-off-by: Jacob Shin <jacob.shin@amd.com>
Link: http://lkml.kernel.org/r/1353123563-3103-12-git-send-email-yinghai@kernel.org
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
arch/x86/include/asm/page_types.h
arch/x86/kernel/cpu/amd.c
arch/x86/platform/efi/efi.c