[PATCH v2] ARM: head-common.S: relocate atags area if necessary

Daniel Mack zonque at gmail.com
Sat Oct 19 12:10:16 EDT 2013


On 10/19/2013 05:15 PM, Nicolas Pitre wrote:
> On Fri, 18 Oct 2013, Russell King - ARM Linux wrote:
> 
>> When things were at a fixed location, they were always placed at
>> around 256 bytes into the memory, below the kernel.  I guess now people
>> are placing them at some random location elsewhere.
>>
>> This is becoming more a more of a pain.  We have all sorts of randomly
>> placed objects in memory now that its only a matter of time before we
>> hit something.  We keep on dreaming up these "well, let's move it"
>> solutions but does that really help?  Move it to where?  Another place
>> where we think there isn't going to be anything?  What if there is?
> 
> This is why I suggested adding a recommendation for placing the 
> initrd/DTB/ATAGs above the 128MB boundary from start of RAM in the ARM 
> booting document.
> 
> The zImage code does have to take into account the location of the final 
> kernel's .bss area in order to properly accommodate appended DTB to 
> zImage, otherwise the simple relocation of the decompressor (with its 
> appended DTB) out of the way of the final kernel image is not sufficient 
> to guarantee that the appended DTB won't be overwritten.
> 
> But I think that this is the extent of what we should do.  We already 
> don't relocate the initrd if it is in the way either.  Trying to make 
> everything automagically relocate properly in all cases during very 
> early boot is very difficult, so it is best to simply not attempt it.

Well, I totally see your point. However, we have machines out there that
won't update via kexec due to this, and fixing kexec is unfortunately
not an option, as updating anything would involve kexec'ing into an
update kernel again. So out only chance is to fix up the dtb location in
early boot code.

You might say my case is special, and you're most probably right. I see
that trying to fix things is opening a can of worms.

So - no worries, we'll just keep that patch around locally as it 'works
for me' (tm) :)


Daniel




More information about the linux-arm-kernel mailing list