From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oupton@kernel.org>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH 3/3] arm64: Unconditionally enable EPAN support
Date: Thu, 22 Jan 2026 11:06:37 +0000 [thread overview]
Message-ID: <86tswdc3eq.wl-maz@kernel.org> (raw)
In-Reply-To: <aXH43Dr-5OrXNOyy@willie-the-truck>
On Thu, 22 Jan 2026 10:15:56 +0000,
Will Deacon <will@kernel.org> wrote:
>
> On Wed, Jan 07, 2026 at 06:07:01PM +0000, Marc Zyngier wrote:
> > While FEAT_PAN3 is pretty recent, having it permanently enabled costs
> > exactly nothing, and does help with exec-only mappings on these fancy
> > ARMv9.2 machines that are rumoured to exist.
>
> I'm not sure it's _entirely_ accurate to say this one costs us "exactly
> nothing":
>
> > diff --git a/arch/arm64/include/asm/cpucaps.h b/arch/arm64/include/asm/cpucaps.h
> > index 177c691914f87..13c0fa54ea19f 100644
> > --- a/arch/arm64/include/asm/cpucaps.h
> > +++ b/arch/arm64/include/asm/cpucaps.h
> > @@ -19,8 +19,6 @@ cpucap_is_possible(const unsigned int cap)
> > "cap must be < ARM64_NCAPS");
> >
> > switch (cap) {
> > - case ARM64_HAS_EPAN:
> > - return IS_ENABLED(CONFIG_ARM64_EPAN);
> > case ARM64_SVE:
> > return IS_ENABLED(CONFIG_ARM64_SVE);
> > case ARM64_SME:
>
> as this means cpus_have_cap(EPAN) always ends up doing a test_bit(). It's
> not exactly expensive, but it feels a little premature when compared to
> PAN and LSE so I'll probably just take those changes for now.
Ah, fair enough. It can probably wait another few years then!
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-01-22 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 18:06 [PATCH 0/3] arm64: Unconditionally compile LSE/PAN/EPAN support Marc Zyngier
2026-01-07 18:06 ` [PATCH 1/3] arm64: Unconditionally enable LSE support Marc Zyngier
2026-01-07 18:07 ` [PATCH 2/3] arm64: Unconditionally enable PAN support Marc Zyngier
2026-01-22 11:21 ` Marc Zyngier
2026-01-22 17:02 ` Will Deacon
2026-01-07 18:07 ` [PATCH 3/3] arm64: Unconditionally enable EPAN support Marc Zyngier
2026-01-22 10:15 ` Will Deacon
2026-01-22 11:06 ` Marc Zyngier [this message]
2026-01-22 16:59 ` [PATCH 0/3] arm64: Unconditionally compile LSE/PAN/EPAN support Will Deacon
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=86tswdc3eq.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=oupton@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--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