should kernel image destination address be picked up by kernel itself?

Ming Lei mlei at Brocade.COM
Tue Feb 10 16:34:32 EST 2009

>> "Ming Lei" <mlei at Brocade.COM> writes:
>> Hi Eric,
>> Do you know what's this purgatory directory for? I saw it is linked
>> kexec in a weird way.

>Yep.  That is the relocatable code that run between one kernel and the

Is there any doc or email thread explain this purgatory and its purpose?

>> Another note for current code base is that there is merged directory
>> arch/powerpc since linux kernel 2.6.23, but kexec-tools still has ppc
>> and ppc64 separated. Is there anyone working on this merged arch?

>Userspace should not be affected by a kernel implementation detail
>like that.

Now linux kernel uses arch/powerpc to have both ppc32 and ppc64 code
together. Should I use arch/ppc in kexec-tools, then it wont work with
kernel powerpc since it uses device tree blob; if I use arch/ppc64 in
kexec-tools, then since I need to use for ppc32, it wont work too. Right
now it is not an immediate problem because we don't have any
ppc32(except these few old ppc32). Howver, there is working in progress
to support kexec/kdump for freescale 85xx(it is 32bit ppc). We may need
to address the problem in kexec-tools.


More information about the kexec mailing list