From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Baoquan He <bhe@redhat.com>
Cc: kexec@lists.infradead.org, linux-doc@vger.kernel.org,
vgoyal@redhat.com, dyoung@redhat.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-debuggers@vger.kernel.org,
stephen.s.brennan@oracle.com, kernel@gpiccoli.net,
kernel-dev@igalia.com
Subject: Re: [PATCH V2] Documentation: Improve crash_kexec_post_notifiers description
Date: Wed, 11 Sep 2024 17:09:11 +0200 [thread overview]
Message-ID: <d954da78-87cf-d7d9-a620-0c2fae5dd242@igalia.com> (raw)
In-Reply-To: <ZtUrX4n+HPYhyQ9z@MiWiFi-R3L-srv>
On 02/09/2024 05:05, Baoquan He wrote:
> On 08/30/24 at 03:21pm, Guilherme G. Piccoli wrote:
>> Be more clear about the downsides, the upsides (yes, there are some!)
>> and about code that unconditionally sets that.
>>
>> Reviewed-by: Stephen Brennan <stephen.s.brennan@oracle.com>
>> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
>>
>> ---
>>
>> V2: Some wording improvements from Stephen, thanks!
>> Also added his review tag.
>>
>> V1 link: https://lore.kernel.org/r/20240830140401.458542-1-gpiccoli@igalia.com/
>>
>>
>> Documentation/admin-guide/kernel-parameters.txt | 16 ++++++++++------
>> 1 file changed, 10 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
>> index efc52ddc6864..351730108c58 100644
>> --- a/Documentation/admin-guide/kernel-parameters.txt
>> +++ b/Documentation/admin-guide/kernel-parameters.txt
>> @@ -913,12 +913,16 @@
>> the parameter has no effect.
>>
>> crash_kexec_post_notifiers
>> - Run kdump after running panic-notifiers and dumping
>> - kmsg. This only for the users who doubt kdump always
>> - succeeds in any situation.
>> - Note that this also increases risks of kdump failure,
>> - because some panic notifiers can make the crashed
>> - kernel more unstable.
>> + Only jump to kdump kernel after running the panic
>> + notifiers and dumping kmsg. This option increases the
>> + risks of a kdump failure, since some panic notifiers
>> + can make the crashed kernel more unstable. In the
>> + configurations where kdump may not be reliable,
>> + running the panic notifiers can allow collecting more
>> + data on dmesg, like stack traces from other CPUS or
>> + extra data dumped by panic_print. Notice that some
>> + code enables this option unconditionally, like
>> + Hyper-V, PowerPC (fadump) and AMD SEV.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> I know Hyper-V enable panic-notifiers by default, but don't remember how
> PowerPC and AMD SEC behave in this aspect. While at it, can you add a
> little more words to state them in log so that people can learn it?
> Thanks.
>
Hi Baoquan, tnx for the suggestion! You mean mention that in the commit
message? If so, I can certainly do - will sent a new version soon(tm)
and include it =)
Cheers,
Guilherme
next prev parent reply other threads:[~2024-09-11 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 18:21 Guilherme G. Piccoli
2024-09-02 3:05 ` Baoquan He
2024-09-11 15:09 ` Guilherme G. Piccoli [this message]
2024-09-12 0:54 ` Baoquan He
2024-09-02 8:23 ` Simon Horman
2024-09-11 15:10 ` Guilherme G. Piccoli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d954da78-87cf-d7d9-a620-0c2fae5dd242@igalia.com \
--to=gpiccoli@igalia.com \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=kexec@lists.infradead.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen.s.brennan@oracle.com \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®