Thread (2 messages) 2 messages, 2 authors, 2015-08-04

RE: [RFC V2 PATCH 0/1] kexec: crash_kexec_post_notifiers boot option related fixes

From: 河合英宏 / KAWAI,HIDEHIRO <hidden>
Date: 2015-08-04 11:41:20
Also in: kexec, lkml

Hello,

Thanks for the reply.
From: Eric W. Biederman [mailto:ebiederm@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?

Regards,
Kawai
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help