On Wed, Oct 01, 2014 at 05:16:21PM +0100, Mark Rutland wrote: [..] > I'm still rather unhappy about the mechanism by which the DTB is passed > by userspace and detected by the kernel, as I'd prefer that the user > explictly stated which segment they wanted to pass to the (Linux) > kernel, but that would require reworking the kexec syscall to allow > per-segment info/flags. Why does the running kernel need to know about dtb segment. I see following. ldr x0, kexec_dtb_addr IIUC, we are loading this address in x0. Can't we do something similar in user space with purgatory. I mean first jump to purgatory (code compiled in user space but runs prviliged) and that code takes care of loading x0 with right dtb addr and then jump to final kernel. IOW, I am not able to understand that why kernel implementation needs to know which is dtb segment. Thanks Vivek
