diff options
| author | WANG Chao <chaowang@redhat.com> | 2014-04-22 10:56:43 +0800 |
|---|---|---|
| committer | Simon Horman <horms@verge.net.au> | 2014-04-23 09:11:03 +0900 |
| commit | c084ccc4f08f40b87a5e8d4c58c19edb3aa43ba1 (patch) | |
| tree | f2d2ecbcd2e52c44fdd21ad348cf72960a20edc2 /purgatory/printf.c | |
| parent | 44c1f9ede814889f4921b400571219188619d6f6 (diff) | |
x86, cleanup: increase CRASH_MAX_MEMMAP_NR up to 1024
CRASH_MAX_MEMMAP_NR is used as the upper boundary of memmap_p.
Originally memmap_p was used to store RANGE_RAM only. But now we changed
it to store all the types of memory ranges for 2nd kernel, which
includes RANGE_RAM, RANGE_ACPI, RANGE_ACPI_NVS (and RANGE_RESERVED in
the future).
Currently CRASH_MAX_MEMMAP_NR is defined (KEXEC_MAX_SEGMENTS + 2), which
is not enough for memmap_p. It must be increased to a much higher value.
I think 1024 is good enough for storing all memory ranges for 2nd
kernel. So this patch increases CRASH_MAX_MEMMAP_NR to 1024.
Signed-off-by: WANG Chao <chaowang@redhat.com>
Acked-by: Dave Young <dyoung@redhat.com>
Tested-by: Linn Crosetto <linn@hp.com>
Signed-off-by: Simon Horman <horms@verge.net.au>
Diffstat (limited to 'purgatory/printf.c')
0 files changed, 0 insertions, 0 deletions