[RFC PATCH 0/4] Add device-tree support to kexec-tools for ARM
matthew.leach at arm.com
Thu Sep 6 07:04:50 EDT 2012
I have been having some issues using kexec with your dtb patches...
> Thanks. It was that part of the code that I spent the bulk of my time
> And although it is still has a few rough edges I would be happy for it
> to be used.
I have looked at the output from your generic fs2dt and compared
it to the original dts and all looks okay so I'm happy that this
part of your code works fine.
> I would prefer to avoid requiring kernel changes unless necessary -
> the kernels some of the boards I work with require DT since 3.5.
> However, I am happy to discuss this further, there certainly is
> merit to a clean implementation.
I believe that you are loading the dtb at an offset from the base
of 0x1000, this is where the problem lies in that the dtb can be
corrupted by the page tables of the decompressor.
Also, device trees can contain firmware and as such be on the
order of megabytes in size. This could potentially corrupt the
decompressor image depending upon the order that these two blobs
are written to memory.
I suggest that we put the DTB out of the way, perhaps just after
the initrd segment, or at the initrd_offset in the case that
there is no initrd. This would require a kernel change to set the
correct parameter to the relocate_new_kerenel function, but the
change is minimal.
If you are happy with this, I have a set of patches that does the
More information about the kexec