From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Marc Zyngier <maz@kernel.org>
Cc: catalin.marinas@arm.com, will@kernel.org, broonie@kernel.org,
oliver.upton@linux.dev, ardb@kernel.org, frederic@kernel.org,
james.morse@arm.com, joey.gouly@arm.com,
scott@os.amperecomputing.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] arm64: cpufeature: add FEAT_LSUI
Date: Wed, 11 Jun 2025 18:55:41 +0100 [thread overview]
Message-ID: <aEnDHerp45syb8iO@e129823.arm.com> (raw)
In-Reply-To: <861prqe2bp.wl-maz@kernel.org>
Hi Marc,
> On Wed, 11 Jun 2025 11:49:11 +0100,
> Yeoreum Yun <yeoreum.yun@arm.com> wrote:
> >
> > Since Armv9.6, FEAT_LSUI supplies load/store instructions
> > for privileged level to access user memory without clearing PSTATE.PAN bit.
> >
> > Add LSUI feature so that the unprevilieged load/store instrcutions
>
> nit: instructions
Thanks.
> > could be used when kernel accesses user memory without clearing PSTATE.PAN bit.
> >
> > Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
> > ---
> > arch/arm64/kernel/cpufeature.c | 8 ++++++++
> > arch/arm64/tools/cpucaps | 1 +
> > 2 files changed, 9 insertions(+)
> >
> > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> > index b34044e20128..d914982c7cee 100644
> > --- a/arch/arm64/kernel/cpufeature.c
> > +++ b/arch/arm64/kernel/cpufeature.c
> > @@ -278,6 +278,7 @@ static const struct arm64_ftr_bits ftr_id_aa64isar2[] = {
> >
> > static const struct arm64_ftr_bits ftr_id_aa64isar3[] = {
> > ARM64_FTR_BITS(FTR_VISIBLE, FTR_NONSTRICT, FTR_LOWER_SAFE, ID_AA64ISAR3_EL1_FPRCVT_SHIFT, 4, 0),
> > + ARM64_FTR_BITS(FTR_HIDDEN, FTR_NONSTRICT, FTR_LOWER_SAFE, ID_AA64ISAR3_EL1_LSUI_SHIFT, 4, ID_AA64ISAR3_EL1_LSUI_NI),
> > ARM64_FTR_BITS(FTR_VISIBLE, FTR_NONSTRICT, FTR_LOWER_SAFE, ID_AA64ISAR3_EL1_FAMINMAX_SHIFT, 4, 0),
> > ARM64_FTR_END,
> > };
>
> Please enable the equivalent bits in KVM so that the feature can be
> exposed to a guest.
Okay. I'll add in next round.
Thanks!
--
Sincerely,
Yeoreum Yun
next prev parent reply other threads:[~2025-06-11 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 10:49 [PATCH 0/6] support FEAT_LSUI and apply it on futex atomic ops Yeoreum Yun
2025-06-11 10:49 ` [PATCH 1/6] arm64: cpufeature: add FEAT_LSUI Yeoreum Yun
2025-06-11 13:29 ` Mark Brown
2025-06-11 14:52 ` Yeoreum Yun
2025-06-11 15:16 ` Marc Zyngier
2025-06-11 17:55 ` Yeoreum Yun [this message]
2025-06-11 10:49 ` [PATCH 2/6] arm64/Kconfig: add LSUI Kconfig Yeoreum Yun
2025-06-11 13:34 ` Mark Brown
2025-06-11 14:48 ` Yeoreum Yun
2025-06-11 15:17 ` Marc Zyngier
2025-06-11 17:54 ` Yeoreum Yun
2025-06-12 6:33 ` Marc Zyngier
2025-06-11 10:49 ` [PATCH 3/6] arm64/futex: move futex atomic logic with clearing PAN bit Yeoreum Yun
2025-06-11 10:49 ` [PATCH 4/6] arm64/futex: add futex atomic operation with FEAT_LSUI Yeoreum Yun
2025-06-11 10:49 ` [PATCH 5/6] arm64/asm: introduce lsui.h Yeoreum Yun
2025-06-11 10:49 ` [PATCH 6/6] arm64/futex: support futex with FEAT_LSUI Yeoreum Yun
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=aEnDHerp45syb8iO@e129823.arm.com \
--to=yeoreum.yun@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=frederic@kernel.org \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=scott@os.amperecomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.