x86, 64bit: Don't set max_pfn_mapped wrong value early on native path
authorYinghai Lu <yinghai@kernel.org>
Thu, 24 Jan 2013 20:19:54 +0000 (12:19 -0800)
committerH. Peter Anvin <hpa@linux.intel.com>
Tue, 29 Jan 2013 23:20:16 +0000 (15:20 -0800)
commit100542306f644fc580857a8ca4896fb12b794d41
treee0884289c69afbc3ec92dd895a9405b03e2168ff
parent6b9c75aca6cba4d99a6e8d8274b1788d4d4b50d9
x86, 64bit: Don't set max_pfn_mapped wrong value early on native path

We are not having max_pfn_mapped set correctly until init_memory_mapping.
So don't print its initial value for 64bit

Also need to use KERNEL_IMAGE_SIZE directly for highmap cleanup.

-v2: update comments about max_pfn_mapped according to Stefano Stabellini.

Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Link: http://lkml.kernel.org/r/1359058816-7615-14-git-send-email-yinghai@kernel.org
Acked-by: Borislav Petkov <bp@suse.de>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
arch/x86/kernel/head64.c
arch/x86/kernel/setup.c
arch/x86/mm/init_64.c