On Wed, Mar 07, 2007 at 06:01:22PM +0900, Horms wrote:
> On Wed, Mar 07, 2007 at 01:52:18PM +0530, Vivek Goyal wrote:
> > 
> > o Load purgatory below 2G while loading bzImage. x86_64 purgatory got
> >   relocation types R_X86_64_32S hence got to be below 2G.
> 
> Thanks. I've applied this. However the grammar in the comment seems a
> little weird to me.  Is the patch below an improvement?
> 

Sorry, Actually I should have been more descriptive. With i386 kernel being
relocatable, we modified the bzImage loader code in kexec-tools to load
purgatory anywhere within 4G. And we try to load it nearer to end of 
available memory so that we are as far away as possible from kernel. 

This worked for i386 and purgatory location will be close to 4G. (If valid
RAM is available.). But same code failed while trying to load x86_64
relocatable bzImage. There are relocations present in purgatory of type
R_X86_64_32S, and if we load it above 2G, we can't process these relocations.
I get a warning from kexec-tools while loading relocatable x86_64 image.

Something like.

overflow in relocation type R_X86_64_32 val 237ff7100

So I limited the location of purgatory to be within first 2G to avoid this
problem.

Thanks
Vivek
_______________________________________________
fastboot mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/fastboot

Reply via email to