From: Ada Couprie Diaz <ada.coupriediaz@arm.com>
To: linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Vladimir Murzin <vladimir.murzin@arm.com>,
Marc Zyngier <maz@kernel.org>, Kiryl Shutsemau <kas@kernel.org>,
Breno Leitao <leitao@debian.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
Doug Anderson <dianders@chromium.org>,
Linus Walleij <linusw@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Huth <thuth@redhat.com>, Dawei Li <dawei.li@linux.dev>,
mrigendrachaubey <mrigendra.chaubey@gmail.com>,
kernel-team@meta.com, linux-kernel@vger.kernel.org,
Ada Couprie Diaz <ada.coupriediaz@arm.com>
Subject: [PATCH 0/3] arm64: sdei: fix entry edge cases, pseudo-NMI
Date: Tue, 17 Nov 2026 17:48:11 +0000 [thread overview]
Message-ID: <20261117174814.95936-1-ada.coupriediaz@arm.com> (raw)
Hi,
As discussed in [0], SDEI entry has a number of remaining issues.
This small series aims to fix the biggest potential issues :
- Patch 1 : with KVM in VHE, VBAR_EL1 might not be correct
- Patch 2 : PMR was not handled at all when using pseudo-NMI
- Patch 3 : very early SDEI interrupt might end up with `current == NULL`
I have booted the patches, but I don't have an SDEI test setup yet,
so I would really appreciate real-world testing that nothing breaks while
I set up something, /especially/ with `CONFIG_ARM64_PSEUDO_NMI=y` and
`irqchip.gicv3_pseudo_nmi=1` given the new PMR handling !
Contrary to what I said in [0], patch 1 and 2 fix things in C rather than
in entry.S. SDEI is already a special case and very edge-case-y, so
as we cannot really hope to share code with the regular entry path,
we might as well handle the edge cases that we can in C.
I think everything should be easily backportable if needed, though patch 3
depends on commit 3d8c1a013d78 ("arm64: smp: initialize cpu offset
earlier") which I don't think is in the 5.10 tree.
There are a couple of possible un-addressed issues still:
- SWPAN is not handled on SDEI entry, but users of both SDEI and SWPAN
are quite unlikely. Given that SDEI can interrupt anything at any time,
and SWPAN is already very fiddly because of non-atomic register
accesses, we might disallow the combination if it causes issues ;
- Pointer Authentication is not handled either, but is not covered here as
it does not present an immediate functionnal issue.
Thanks in advance
Ada
Based on v7.4-rc3
[0]: https://lore.kernel.org/r/20261105120835.3321912-1-kirill@shutemov.name
Ada Couprie Diaz (3):
arm64: entry: sdei: always set VBAR_EL1 on SDEI entry
arm64: entry: sdei: save and restore PMR for pseudo-NMI
arm64: head: set __entry_task along with task setup
arch/arm64/kernel/entry-common.c | 40 ++++++++++++++++++++++----------
arch/arm64/kernel/head.S | 3 +++
arch/arm64/kernel/process.c | 3 ---
3 files changed, 31 insertions(+), 15 deletions(-)
base-commit: aebb7274476403040d582c61478df8f4a7bf9cd3
--
2.43.0
next reply other threads:[~2026-11-17 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 17:48 Ada Couprie Diaz [this message]
2026-11-17 17:48 ` [PATCH 1/3] arm64: entry: sdei: always set VBAR_EL1 on SDEI entry Ada Couprie Diaz
2026-11-17 17:48 ` [PATCH 2/3] arm64: entry: sdei: save and restore PMR for pseudo-NMI Ada Couprie Diaz
2026-11-18 9:58 ` Vladimir Murzin
2026-11-17 17:48 ` [PATCH 3/3] arm64: head: set __entry_task along with task setup Ada Couprie Diaz
2026-11-18 11:01 ` Vladimir Murzin
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=20261117174814.95936-1-ada.coupriediaz@arm.com \
--to=ada.coupriediaz@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dawei.li@linux.dev \
--cc=dianders@chromium.org \
--cc=kas@kernel.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mrigendra.chaubey@gmail.com \
--cc=peterz@infradead.org \
--cc=ruanjinjie@huawei.com \
--cc=thuth@redhat.com \
--cc=vladimir.murzin@arm.com \
--cc=will@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®