[RFC V2 PATCH 0/1] kexec: crash_kexec_post_notifiers boot option related fixes
河合英宏 / KAWAI，HIDEHIRO
hidehiro.kawai.ez at hitachi.com
Tue Aug 4 04:41:14 PDT 2015
Thanks for the reply.
> From: Eric W. Biederman [mailto:ebiederm at xmission.com]
> A specific hook for a very specific purpose when there is no other way
> we can consider.
So, is kmsg_dump like feature admissible?
> If you don't have something that generalises well into a general purpose
> operation that it makes sense for everyone to call you can always use
> the world's largest aka you can run code before the new kernel starts
> that is loaded with kexec_load.
One of our purposes, notifying "I'm dying", would be achieved by purgatory
code provided by kexec command as I stated before. Since the way of the
notification will differ from each vendor, I think we need to modify
the purgatory codes pluggable. Also, I think we need some parameter
passing mechanism to the purgatory code. For example, passing the panic
message via boot parameter to save it to SEL. Although I'm not sure
we can do that (I've not investigated well yet). Is that acceptable?
More information about the kexec