From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: mingo@kernel.org, tglx@linutronix.de, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, x86@kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: [GIT PULL] x86 NMI diagnostics for v6.3
Date: Tue, 21 Feb 2023 18:02:18 -0800 [thread overview]
Message-ID: <20230222020218.GA1345108@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello, Linus,
Please pull the x86 NMI diagnostics series from:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/nmi.2023.02.14a
# HEAD: x86/nmi: Print reasons why backtrace NMIs are ignored (2023-01-19 15:55:12 -0800)
This is of course not normally something that would come up through the
-rcu tree, but these have Ingo Molnar's Reviewed-by tag.
----------------------------------------------------------------
NMI diagnostics for v6.3
Add diagnostics to the x86 NMI handler to help detect NMI-handler bugs
on the one hand and failing hardware on the other.
----------------------------------------------------------------
Paul E. McKenney (2):
x86/nmi: Accumulate NMI-progress evidence in exc_nmi()
x86/nmi: Print reasons why backtrace NMIs are ignored
arch/x86/kernel/nmi.c | 108 +++++++++++++++++++++++++++++++++++++++++++++++++-
include/linux/nmi.h | 8 ++++
lib/Kconfig.debug | 11 +++++
lib/nmi_backtrace.c | 2 +
4 files changed, 128 insertions(+), 1 deletion(-)
next reply other threads:[~2023-02-22 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 2:02 Paul E. McKenney [this message]
2023-02-23 18:47 ` pr-tracker-bot
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=20230222020218.GA1345108@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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®