diff options
author | Magnus Damm <magnus@valinux.co.jp> | 2006-11-14 16:57:46 +0100 |
---|---|---|
committer | Andi Kleen <andi@basil.nowhere.org> | 2006-11-14 16:57:46 +0100 |
commit | 15803a43288da434d34d41c4ed650c3c1728d42c (patch) | |
tree | 6294e8d6a95e329c6cae85ff07f0e2459e76971d /Documentation | |
parent | 5e58a02a8f6a7a1c9ae41f39286bcd3aea0d6f24 (diff) |
[PATCH] x86-64: setup saved_max_pfn correctly (kdump)
x86_64: setup saved_max_pfn correctly
2.6.19-rc4 has broken CONFIG_CRASH_DUMP support on x86_64. It is impossible
to read out the kernel contents from /proc/vmcore because saved_max_pfn is set
to zero instead of the max_pfn value before the user map is setup.
This happens because saved_max_pfn is initialized at parse_early_param() time,
and at this time no active regions have been registered. save_max_pfn is setup
from e820_end_of_ram(), more exact find_max_pfn_with_active_regions() which
returns 0 because no regions exist.
This patch fixes this by registering before and removing after the call
to e820_end_of_ram().
Signed-off-by: Magnus Damm <magnus@valinux.co.jp>
Signed-off-by: Andi Kleen <ak@suse.de>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions