kexec-tools and multiboot breakage
Simon Horman
horms at verge.net.au
Tue Jan 14 22:48:33 EST 2014
On Wed, Jan 15, 2014 at 01:25:49PM +1000, Peter Chubb wrote:
> Hi Simon,
> When you get a moment, please check out
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735360
>
> Quick summary:
> If your kernel is configured to protect the first few pages of
> physical memory, then low memory doesn't start at location 0 --- so
> when scanning the memory ranges from /proc/iomem, the code in
> kexec/arch/i386/kexec-multiboot-x86.c never fills in mem_lower.
>
> I think it's safe to assume that if a memory segment starts at 64k or
> lower, it can be extended to location 0 because of the kernel
> protection on a PC99-style architecture.
Hi Peter,
that approach seems reasonable to me. Could you formally post
the patch to the kexec list with me CCed? I would like a Signed-off-by
line. Thanks.
More information about the kexec
mailing list