summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYinghai Lu <yinghai@kernel.org>2012-11-17 03:38:46 (GMT)
committerH. Peter Anvin <hpa@linux.intel.com>2012-11-17 19:59:07 (GMT)
commitdd7dfad7fb297b1746bcdbebbdc970d723a635bd (patch)
treec3bf09061dc2987c0c472df3a66cc16d55ec6745
parentab9519376e86fbbf3c64e5a2b8b005958ea3e9cc (diff)
downloadlinux-dd7dfad7fb297b1746bcdbebbdc970d723a635bd.tar.xz
x86, mm: Set memblock initial limit to 1M
memblock_x86_fill() could double memory array. If we set memblock.current_limit to 512M, so memory array could be around 512M. So kdump will not get big range (like 512M) under 1024M. Try to put it down under 1M, it would use about 4k or so, and that is limited. Signed-off-by: Yinghai Lu <yinghai@kernel.org> Link: http://lkml.kernel.org/r/1353123563-3103-10-git-send-email-yinghai@kernel.org Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
-rw-r--r--arch/x86/kernel/setup.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 23b079f..4bd8921 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -890,7 +890,7 @@ void __init setup_arch(char **cmdline_p)
cleanup_highmap();
- memblock.current_limit = get_max_mapped();
+ memblock.current_limit = ISA_END_ADDRESS;
memblock_x86_fill();
/*