Skip to content

Commit

Permalink
x86, mm: Set memblock initial limit to 1M
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Yinghai Lu authored and H. Peter Anvin committed Nov 17, 2012
1 parent ab95193 commit dd7dfad
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion arch/x86/kernel/setup.c
Original file line number Diff line number Diff line change
Expand Up @@ -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();

/*
Expand Down

0 comments on commit dd7dfad

Please sign in to comment.