Messages in this thread | | | From | (Eric W. Biederman) | Subject | Re: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage | Date | Sat, 28 Apr 2007 14:18:14 -0600 |
| |
Jeff Garzik <jeff@garzik.org> writes:
> Andi Kleen wrote: >> From: Vivek Goyal <vgoyal@in.ibm.com> >> >> >> o Extend the bzImage protocol (same as i386) to allow bzImage loaders to >> load the protected mode kernel at non-1MB address. Now protected mode >> component is relocatable and can be loaded at non-1MB addresses. >> >> o As of today kdump uses it to run a second kernel from a reserved memory >> area. >> >> Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com> >> Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com> >> Signed-off-by: Andi Kleen <ak@suse.de> > > Can you point to / link to threads where the bootloader folks looked > over the reloc changes from their side, and commented?
Jeff what is your concern.
The boot protocol change is in 2.6.21 for arch/i386.
HPA looked at it a while ago.
All it does is set a flag that tells a bootloader. "Hey. I can run when loaded a non-default address, and this is what you have to align me to."
All relocation processing happens in the kernel itself.
So it is all pretty trivial.
Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |