public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>, 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: Tue, 20 Jan 2026 10:07:33 +0000	[thread overview]
Message-ID: <aW9T5b+Y2b2JOZHk@e129823.arm.com> (raw)
In-Reply-To: <aW9O6R7v-ybhrm66@J2N7QTR9R3>

Hi Mark,

> On Mon, Jan 19, 2026 at 10:32:11PM +0000, Yeoreum Yun wrote:
> > > On Mon, Dec 15, 2025 at 09:56:04AM +0000, Yeoreum Yun wrote:
> > > > > On Sun, 14 Dec 2025 11:22:48 +0000,
> > > > > Yeoreum Yun <yeoreum.yun@arm.com> wrote:
> > > > > >
> > > > > > Apply the FEAT_LSUI instruction to emulate the deprecated swpX
> > > > > > instruction, so that toggling of the PSTATE.PAN bit can be removed when
> > > > > > LSUI-related instructions are used.
> > > > > >
> > > > > > Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
> > > > >
> > > > > It really begs the question: what are the odds of ever seeing a CPU
> > > > > that implements both LSUI and AArch32?
> > > > >
> > > > > This seems extremely unlikely to me.
> > > >
> > > > Well, I'm not sure how many CPU will have
> > > > both ID_AA64PFR0_EL1.EL0 bit as 0b0010 and FEAT_LSUI
> > > > (except FVP currently) -- at least the CPU what I saw,
> > > > most of them set ID_AA64PFR0_EL1.EL0 as 0b0010.
> > >
> > > Just to make sure I understand you, you're saying that you have seen
> > > a real CPU that implements both 32-bit EL0 *and* FEAT_LSUI?
> > >
> > > > If you this seems useless, I don't have any strong comments
> > > > whether drop patches related to deprecated swp instruction parts
> > > > (patch 8-9 only) or not.
> > > > (But, I hope to pass this decision to maintaining perspective...)
> > >
> > > I think it depends on whether or not the hardware exists. Marc thinks
> > > that it's extremely unlikely whereas you appear to have seen some (but
> > > please confirm).
> >
> > What I meant was not a 32-bit CPU with LSUI, but a CPU that supports
> > 32-bit EL0 compatibility (i.e. ID_AA64PFR0_EL1.EL0 = 0b0010).
> > My point was that if CPUs implementing LSUI do appear, most of them will likely
> > continue to support the existing 32-bit EL0 compatibility that
> > the majority of current CPUs already have.
>
> That doesn't really answer Will's question. Will asked:
>
>   Just to make sure I understand you, you're saying that you have seen a
>   real CPU that implements both 32-bit EL0 *and* FEAT_LSUI?
>
> IIUC you have NOT seen any specific real CPU that supports this, and you
> have been testing on an FVP AEM model (which can be configured to
> support this combination of features). Can you please confirm?
>
> I don't beleive it's likely that we'll see hardware that supports
> both FEAT_LSUI and AArch32 (at EL0).

Yes. I've tested in FVP model. and the latest of my reply said
I confirmed that Marc's and your view was right.

Thanks.

--
Sincerely,
Yeoreum Yun


  reply	other threads:[~2026-01-20 10:09 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 [this message]
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
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=aW9T5b+Y2b2JOZHk@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