[lkml]   [2007]   [Apr]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage
Jeff Garzik <> writes:

> Andi Kleen wrote:
>> From: Vivek Goyal <>
>> 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 <>
>> Signed-off-by: Vivek Goyal <>
>> Signed-off-by: Andi Kleen <>
> 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-04-28 22:23    [W:0.187 / U:5.416 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site