On Tue, Oct 07, 2014 at 09:12:57PM +0100, Geoff Levand wrote: > Hi Vivek, > > On Tue, 2014-10-07 at 14:45 -0400, Vivek Goyal wrote: > > On Tue, Oct 07, 2014 at 11:42:00AM -0700, Geoff Levand wrote: > > > Adding purgatory code to arm64 is low priority, and I currently > > > have no plan to do that. Users are asking for kdump, and proper > > > UEFI support, so that is what I will work towards. > > > > I think having purgatory enabled is very important here as in kernel > > you are hardcoding that one of the segments is DTB and doing all the > > magic tricks w.r.t putting a magic number. > > I don't argue that having purgatory code could be useful, but as of > now, enabling the other features is what I'll work towards. > > Regarding the device tree magic number, I'm wondering if you missed > that the device tree has a header, and that header has a magic > number. See here: > > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/scripts/dtc/libfdt/fdt.h#n6 As I mentioned elsewhere, regardless of whether we can detect if a segment is a DTB, we're still encoding the policy of what to do with that within the kernel, and there are cases that is problematic for. Leaving at least the register setup to the caller's discretion (by way of a userspace provided purgatory) avoids those problems entirely. kexec_load_file is more complicated in that regard due to the less general interface provided. Mark.
