diff options
author | Vivek Goyal <vgoyal@in.ibm.com> | 2005-09-03 15:56:31 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@evo.osdl.org> | 2005-09-05 00:06:09 -0700 |
commit | 484b90c4b965d54037ff99b198d84cdf144f8a35 (patch) | |
tree | 559efa2585ee360e610882724500cbe3d5712d98 /arch/i386/kernel/cpu | |
parent | 5fd75ebb1a58c1a3c9e3d9fdf75ce7286b79bb74 (diff) | |
download | op-kernel-dev-484b90c4b965d54037ff99b198d84cdf144f8a35.zip op-kernel-dev-484b90c4b965d54037ff99b198d84cdf144f8a35.tar.gz |
[PATCH] kdump: Save parameter segment in protected mode (x86)
o With introduction of kexec as boot-loader, the assumption that parameter
segment will always be loaded at lower address than kernel and will be
addressable by early bootup page tables is no longer valid. In kexec on
panic case parameter segment might well be loaded beyond kernel image and
might not be addressable by early boot page tables.
o This case might hit in the scenario where user has reserved a chunk of
memory for second kernel, for example 16MB to 64MB, and has also built
second kernel for physical memory location 16MB. In this case kexec has no
choice but to load the parameter segment at a higher address than new kernel
image at safe location where new kernel does not stomp it.
o Though problem should automatically go away once relocatable kernel for i386
is in place and kexec can determine the location of new kernel at run time
and load parameter segment at lower address than kernel image. But till then
this patch can go in (assuming it does not break something else).
o This patch moves up the boot parameter saving code. Now boot parameters
are copied out in protected mode before page tables are initialized. This
will ensure that parameter segment is always addressable irrespective of
its physical location.
Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/i386/kernel/cpu')
0 files changed, 0 insertions, 0 deletions