From: Marc Zyngier <maz@kernel.org>
To: Yeoreum Yun <yeoreum.yun@arm.com>
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 2/6] arm64/Kconfig: add LSUI Kconfig
Date: Thu, 12 Jun 2025 07:33:46 +0100 [thread overview]
Message-ID: <87ikl1foz9.wl-maz@kernel.org> (raw)
In-Reply-To: <aEnC6img102ZygDy@e129823.arm.com>
On Wed, 11 Jun 2025 18:54:50 +0100,
Yeoreum Yun <yeoreum.yun@arm.com> wrote:
>
> Hi Marc,
>
> > On Wed, 11 Jun 2025 11:49:12 +0100,
> > Yeoreum Yun <yeoreum.yun@arm.com> wrote:
> > >
> > > Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
> > > previleged level to access to access user memory without clearing
> > > PSTATE.PAN bit.
> > > It's enough to add CONFIG_AS_HAS_LSUI only because the code for LUSI uses
> > > indiviual `.arch_extension` entries.
> > >
> > > Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
> > > ---
> > > arch/arm64/Kconfig | 8 +++++++-
> > > 1 file changed, 7 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> > > index 55fc331af337..20f360eef2ac 100644
> > > --- a/arch/arm64/Kconfig
> > > +++ b/arch/arm64/Kconfig
> > > @@ -2237,6 +2237,13 @@ config ARM64_GCS
> > >
> > > endmenu # "v9.4 architectural features"
> > >
> > > +menu "v9.6 architectural features"
> > > +
> > > +config AS_HAS_LSUI
> > > + def_bool $(as-instr,.arch_extension lsui)
> > > +
> > > +endmenu # "v9.6 architectural features"
> > > +
> > > config ARM64_SVE
> > > bool "ARM Scalable Vector Extension support"
> > > default y
> > > @@ -2498,4 +2505,3 @@ endmenu # "CPU Power Management"
> > > source "drivers/acpi/Kconfig"
> > >
> > > source "arch/arm64/kvm/Kconfig"
> > > -
> >
> > Can you please document what toolchain versions have support for this?
> >
> > Thanks,
>
> Okay. But here with comment or Is any other suggested place for
> this?
The help section in the Kconfig option you are introducing would be a
good start.
Thanks,
M.
--
Jazz isn't dead. It just smells funny.
next prev parent reply other threads:[~2025-06-12 6:36 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
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 [this message]
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=87ikl1foz9.wl-maz@kernel.org \
--to=maz@kernel.org \
--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=oliver.upton@linux.dev \
--cc=scott@os.amperecomputing.com \
--cc=will@kernel.org \
--cc=yeoreum.yun@arm.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 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.