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

2006-11-17 Thread Vivek Goyal
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-1M

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

2006-11-17 Thread H. Peter Anvin
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 no

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

2006-11-17 Thread Vivek Goyal
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

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

2006-11-17 Thread H. Peter Anvin
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 reserv

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

2006-11-17 Thread 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. S