On Jan 2, 2009, at 8:08 AM, M. Mohan Kumar wrote:

Support for relocatable kernel in kexec-tools

This patch is based on the patch sent by Milton Miller with the subject [PATCH 1/2
 kexec-tools] ppc64: new relocatble kernel activation ABI

http://patchwork.ozlabs.org/patch/5378/

Even with the above patch, the relocatable kernel always move to physical address 0 (ie PHYSICAL_START). Following patch fixes this problem by marking a local variable to 1 in purgatory during kdump kernel load time (kexec -p). After a crash, purgatory sets __run_at_load variable location in the kernel to 1 if the local variable is set to 1. So that the kernel will be running
as a relocatable kernel.

Signed-off-by: M. Mohan Kumar <[email protected]>
Signed-off-by: Milton Miller <[email protected]>

your sign-off should have been after mine as you were making changes to my patch.

I actually completed my own testing last night with a slightly different version:

(1) I unconditionally store the purgatory value to the kernel (less maintence if we decide to define further flags in the future).

(2) I use less registers in asm (no need for r18)

(3) I renamed the variable in the c code to be my_run_at_load to be more consistent with the other names.

Also, I have some cleanup patches on top of this one. I'm in the process of setting up a new email client to send my patches, so it will be a few hours yet until I get them posted. But I would appreciate waiting for my series so I don't have to rediff the later patches.

thanks,
milton

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Reply via email to