public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	catalin.marinas@arm.com, broonie@kernel.org,
	oliver.upton@linux.dev, miko.lenczewski@arm.com,
	kevin.brodsky@arm.com, ardb@kernel.org, suzuki.poulose@arm.com,
	lpieralisi@kernel.org, yangyicong@hisilicon.com,
	scott@os.amperecomputing.com, joey.gouly@arm.com,
	yuzenghui@huawei.com, pbonzini@redhat.com, shuah@kernel.org,
	arnd@arndb.de, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
	kvm@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v11 RESEND 9/9] arm64: armv8_deprecated: apply FEAT_LSUI for swpX emulation.
Date: Wed, 21 Jan 2026 16:31:28 +0000	[thread overview]
Message-ID: <aXD/YFNirTfoATvN@e129823.arm.com> (raw)
In-Reply-To: <aXD81LT6TX32vlTS@willie-the-truck>

On Wed, Jan 21, 2026 at 04:20:36PM +0000, Will Deacon wrote:
> On Wed, Jan 21, 2026 at 02:51:10PM +0000, Yeoreum Yun wrote:
> > > On Tue, Jan 20, 2026 at 05:59:47PM +0000, Yeoreum Yun wrote:
> > > > On second thought, while a CPU that implements LSUI is unlikely to
> > > > support AArch32 compatibility,
> > > > I don't think LSUI requires the absence of AArch32.
> > > > These two are independent features (and in fact our FVP reports/supports both).
> > >
> > > Did you have to configure the FVP specially for this or that a "default"
> > > configuration?
> > >
> > > > Given that, I'm not sure a WARN is really necessary.
> > > > Would it be sufficient to just drop the patch for swpX instead?
> > >
> > > Given that the whole point of LSUI is to remove the PAN toggling, I think
> > > we should make an effort to make sure that we don't retain PAN toggling
> > > paths at runtime that could potentially be targetted by attackers. If we
> > > drop the SWP emulation patch and then see that we have AArch32 at runtime,
> > > we should forcefully disable the SWP emulation but, since we don't actually
> > > think we're going to see this in practice, the WARN seemed simpler.
> >
> > TBH, I missed the FVP configuration option clusterX.max_32bit_el, which
> > can disable AArch32 support by setting it to -1 (default: 3).
> > Given this, I think it’s reasonable to emit a WARN when LSUI is enabled and
> > drop the SWP emulation path under that condition.
>
> I'm asking about the default value.
>
> If Arm are going to provide models that default to having both LSUI and
> AArch32 EL0 supported, then the WARN is just going to annoy people.
>
> Please can you find out whether or not that's the case?

Yes. I said the deafult == 3 which means that allow to execute
32-bit in EL0 to EL3 (IOW, ID_AA64PFR0_EL1.EL0 == 0b0010)
-- but sorry for lack of explanation.

When I check the latest model's default option value related for this
based on FVP version 11.30
(https://developer.arm.com/Tools%20and%20Software/Fixed%20Virtual%20Platforms/Arm%20Architecture%20FVPs),

  - cluster0.has_lsui=1 default = '0x1'    : Implement additional load and store unprivileged instructions (FEAT_LSUI).
  - cluster0.max_32bit_el=3 default = '0x3'    : Maximum exception level supporting AArch32 modes. -1: No Support for A32 at any EL, x:[0:3] - All the levels below supplied ELx supports A32 : [0xffffffffffffffff:0x3]

So it would be a annoying to people.

--
Sincerely,
Yeoreum Yun


  reply	other threads:[~2026-01-21 16:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-14 11:22 [PATCH v11 RESEND 0/9] support FEAT_LSUI Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 1/9] arm64: cpufeature: add FEAT_LSUI Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 2/9] KVM: arm64: expose FEAT_LSUI to guest Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 3/9] KVM: arm64: kselftest: set_id_regs: add test for FEAT_LSUI Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 4/9] arm64: Kconfig: Detect toolchain support for LSUI Yeoreum Yun
2026-01-19 15:50   ` Will Deacon
2026-01-19 15:54     ` Mark Brown
2026-01-20 11:35       ` Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 5/9] arm64: futex: refactor futex atomic operation Yeoreum Yun
2026-01-19 15:57   ` Will Deacon
2026-01-19 22:19     ` Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 6/9] arm64: futex: support futex with FEAT_LSUI Yeoreum Yun
2026-01-19 16:37   ` Will Deacon
2026-01-19 22:17     ` Yeoreum Yun
2026-01-20 15:44       ` Yeoreum Yun
2026-01-21 13:48       ` Will Deacon
2026-01-21 14:16         ` Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 7/9] arm64: separate common LSUI definitions into lsui.h Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 8/9] arm64: armv8_deprecated: convert user_swpX to inline function Yeoreum Yun
2025-12-14 11:22 ` [PATCH v11 RESEND 9/9] arm64: armv8_deprecated: apply FEAT_LSUI for swpX emulation Yeoreum Yun
2025-12-15  9:33   ` Marc Zyngier
2025-12-15  9:56     ` Yeoreum Yun
2026-01-19 15:34       ` Will Deacon
2026-01-19 22:32         ` Yeoreum Yun
2026-01-20  9:32           ` Yeoreum Yun
2026-01-20  9:46           ` Mark Rutland
2026-01-20 10:07             ` Yeoreum Yun
2026-01-20 11:50               ` Will Deacon
2026-01-20 12:14                 ` Yeoreum Yun
2026-01-20 17:59                 ` Yeoreum Yun
2026-01-21 13:56                   ` Will Deacon
2026-01-21 14:51                     ` Yeoreum Yun
2026-01-21 16:20                       ` Will Deacon
2026-01-21 16:31                         ` Yeoreum Yun [this message]
2026-01-21 16:36                           ` Will Deacon
2026-01-21 16:51                             ` Yeoreum Yun
2025-12-31 10:07 ` [PATCH v11 RESEND 0/9] support 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=aXD/YFNirTfoATvN@e129823.arm.com \
    --to=yeoreum.yun@arm.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kevin.brodsky@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=miko.lenczewski@arm.com \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=scott@os.amperecomputing.com \
    --cc=shuah@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    --cc=yangyicong@hisilicon.com \
    --cc=yuzenghui@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox