From: Jonathan Corbet <corbet@lwn.net>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
kexec@lists.infradead.org, linux-doc@vger.kernel.org
Cc: kernel-dev@igalia.com, bhe@redhat.com, mhklinux@outlook.com,
kernel@gpiccoli.net, linux-kernel@vger.kernel.org,
stephen.s.brennan@oracle.com, horms@kernel.org,
dyoung@redhat.com, vgoyal@redhat.com,
linux-debuggers@vger.kernel.org
Subject: Re: [PATCH V4] Documentation: Improve crash_kexec_post_notifiers description
Date: Mon, 04 Nov 2024 12:29:12 -0700 [thread overview]
Message-ID: <87ed3q94s7.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241027204159.985163-1-gpiccoli@igalia.com>
"Guilherme G. Piccoli" <gpiccoli@igalia.com> writes:
> The crash_kexec_post_notifiers description could be improved a bit,
> by clarifying its upsides (yes, there are some!) and be more descriptive
> about the downsides, specially mentioning code that enables the option
> unconditionally, like Hyper-V[0], PowerPC (fadump)[1] and more recently,
> AMD SEV-SNP[2].
>
> [0] Commit a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running crash kernel").
> [1] Commit 06e629c25daa ("powerpc/fadump: Fix inaccurate CPU state info in vmcore generated with panic").
> [2] Commit 8ef979584ea8 ("crypto: ccp: Add panic notifier for SEV/SNP firmware shutdown on kdump").
>
> Reviewed-by: Stephen Brennan <stephen.s.brennan@oracle.com>
> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
> ---
Applied, thanks.
jon
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2024-11-04 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 20:36 [PATCH V4] Documentation: Improve crash_kexec_post_notifiers description Guilherme G. Piccoli
2024-10-27 22:35 ` Michael Kelley
2024-11-04 19:29 ` Jonathan Corbet [this message]
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=87ed3q94s7.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=gpiccoli@igalia.com \
--cc=horms@kernel.org \
--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=mhklinux@outlook.com \
--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