Re: [PATCH 19/20] x86_64: Extend bzImage protocol for relocatable kernel

[Vivek Goyal <vgoyal@in.ibm.com>]

On Fri, Nov 17, 2006 at 04:45:46PM -0800, H. Peter Anvin wrote:
> Vivek Goyal wrote:
> >On Fri, Nov 17, 2006 at 04:30:04PM -0800, H. Peter Anvin wrote:
> >>Vivek Goyal wrote:
> >>>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>
> >>Do you have a patch for Documentation/i386/boot.txt as well?
> >>
> >
> >Yes. As documentation is shared between i386 and x86_64, It is already 
> >there
> >in Andi's tree and in -mm. I had pushed that with i386 relocatable bzImage
> >changes.
> >
> >http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc5/2.6.19-rc5-mm2/broken-out/x86_64-mm-extend-bzimage-protocol-for-relocatable-protected-mode-kernel.patch
> >
> 
> Your documentation change is buggy.
> 
> The fields at 0230/4 and 0234/1 are 2.05+ not 2.04+
> 
> Please fix, also please update the last revision date.

Thanks for noticing this. Just now sent a patch in separate thread to fix
this.

Thanks
Vivek
-
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/