From: Ryan Roberts <ryan.roberts@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
James Morse <james.morse@arm.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] Workarounds and optimizations for Neoverse-V3AE
Date: Fri, 19 Sep 2025 15:58:27 +0100 [thread overview]
Message-ID: <20250919145832.4035534-1-ryan.roberts@arm.com> (raw)
Hi All,
I know it's late in the cycle, but I thought I'd try my luck at sneaking this
in.
Neoverse-V3AE has a different MIDR value to Neoverse-V3, but qualifies for the
same workarounds and optimizations ("SSBS not fully self-synchronizing" and
BBML2_NOABORT) so this just adds Neoverse-V3AE wherever Neoverse-V3 appears.
Details in the commits.
The last patch adds Neoverse-3VAE to the BBML2_NOABORT allow list. That will
conflict with the patch you have already queued to add AmpereOne, and with the
patch you said you would do to remove X4. But this is a one-liner so trivial to
resolve.
Applies on v6.17-rc5.
Thanks,
Ryan
Mark Rutland (2):
arm64: cputype: Add Neoverse-V3AE definitions
arm64: errata: Apply workarounds for Neoverse-V3AE
Ryan Roberts (1):
arm64: cpufeature: add Neoverse-V3AE to BBML2 allow list
Documentation/arch/arm64/silicon-errata.rst | 2 ++
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/cputype.h | 2 ++
arch/arm64/kernel/cpu_errata.c | 1 +
arch/arm64/kernel/cpufeature.c | 1 +
5 files changed, 7 insertions(+)
--
2.43.0
next reply other threads:[~2025-09-19 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 14:58 Ryan Roberts [this message]
2025-09-19 14:58 ` [PATCH v1 1/3] arm64: cputype: Add Neoverse-V3AE definitions Ryan Roberts
2025-09-19 14:58 ` [PATCH v1 2/3] arm64: errata: Apply workarounds for Neoverse-V3AE Ryan Roberts
2025-09-19 14:58 ` [PATCH v1 3/3] arm64: cpufeature: add Neoverse-V3AE to BBML2 allow list Ryan Roberts
2025-09-22 13:14 ` [PATCH v1 0/3] Workarounds and optimizations for Neoverse-V3AE Will Deacon
2025-09-22 13:34 ` Ryan Roberts
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=20250919145832.4035534-1-ryan.roberts@arm.com \
--to=ryan.roberts@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox