From: Will Deacon <will@kernel.org>
To: Kiryl Shutsemau <kas@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
James Morse <james.morse@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
Doug Anderson <dianders@chromium.org>,
Petr Mladek <pmladek@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Puranjay Mohan <puranjay@kernel.org>,
Usama Arif <usama.arif@linux.dev>,
Breno Leitao <leitao@debian.org>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Lecopzer Chen <lecopzer@gmail.com>,
Sumit Garg <sumit.garg@kernel.org>,
kernel-team@meta.com, kexec@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/4] arm64: cross-CPU NMI via SDEI
Date: Sun, 26 Jul 2026 14:55:49 +0100 [thread overview]
Message-ID: <amYR5VWHWC1WdFXc@willie-the-truck> (raw)
In-Reply-To: <ak_IRHwd02EjWMf8@thinkstation>
On Thu, Jul 09, 2026 at 05:16:37PM +0100, Kiryl Shutsemau wrote:
> On Mon, Jun 29, 2026 at 04:07:14PM +0100, Kiryl Shutsemau wrote:
> > From: "Kiryl Shutsemau (Meta)" <kas@kernel.org>
> >
> > A class of debug/observability features needs to interrupt a CPU that has
> > its interrupts locally masked: the all-CPU backtrace behind sysrq-l /
> > RCU-stall / hung-task / hard-lockup dumps, and crash_smp_send_stop()
> > capturing a stuck CPU's state into the vmcore. On arm64 these need a
> > mechanism that reaches a CPU spinning with DAIF masked, which a normal IPI
> > cannot.
>
> Gentle ping. Any feedback?
>
> I'm looking forward to finding an upstreamable solution to the problem.
This is all pretty small, self-contained and it's useful to you, so I'm
inclined to merge it.
However, the one vague concern I have is about the direction of SDEI in
the future. AFAIK, the TF-A implementation is known to have issues, it's
not supported at all by R-FA and I worry that the spec is going to fall
behind the architecture, particularly as FEAT_NMI becomes available.
So it would be good to understand what we're signing up to maintain here.
Kiryl, do you see an (eventual) migration over to FEAT_NMI, giving us a
path to deprecating SDEI altogether, or do you think the two will live
alongside each other for the forseeable future?
Cheers,
Will
next prev parent reply other threads:[~2026-07-26 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 15:07 Kiryl Shutsemau
2026-06-29 15:07 ` [PATCH v5 1/4] firmware: arm_sdei: add sdei_is_present() Kiryl Shutsemau
2026-06-30 10:47 ` Usama Arif
2026-06-30 10:57 ` Kiryl Shutsemau
2026-06-29 15:07 ` [PATCH v5 2/4] firmware: arm_sdei: add SDEI_EVENT_SIGNAL support Kiryl Shutsemau
2026-06-30 10:51 ` Usama Arif
2026-06-30 10:58 ` Kiryl Shutsemau
2026-06-29 15:07 ` [PATCH v5 3/4] drivers/firmware: add SDEI cross-CPU NMI service for arm64 Kiryl Shutsemau
2026-06-29 15:07 ` [PATCH v5 4/4] arm64: escalate smp_send_stop() to an SDEI NMI as a last resort Kiryl Shutsemau
2026-07-03 6:01 ` [PATCH v5 0/4] arm64: cross-CPU NMI via SDEI YinFengwei
2026-07-09 16:16 ` Kiryl Shutsemau
2026-07-26 13:55 ` Will Deacon [this message]
2026-07-26 18:35 ` Kiryl Shutsemau
2026-07-28 10:25 ` Will Deacon
2026-07-28 12:17 ` Kiryl Shutsemau
2026-07-29 21:37 ` Doug Anderson
2026-07-30 15:50 ` Kiryl Shutsemau
2026-08-02 12:12 ` Will Deacon
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=amYR5VWHWC1WdFXc@willie-the-truck \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kas@kernel.org \
--cc=kernel-team@meta.com \
--cc=kexec@lists.infradead.org \
--cc=lecopzer@gmail.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=pmladek@suse.com \
--cc=puranjay@kernel.org \
--cc=sumit.garg@kernel.org \
--cc=tglx@linutronix.de \
--cc=usama.arif@linux.dev \
/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®