lkml.org 
[lkml]   [2007]   [Apr]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage
    Date
    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/

    \
     
     \ /
      Last update: 2007-04-28 22:23    [W:0.021 / U:30.032 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site