Re: [PATCH v1 5/6] arm64: cpufeature: Track BBML3 exclusions with erratum options
From: Catalin Marinas
Date: Wed Nov 18 2026 - 12:59:56 EST
On Fri, Nov 13, 2026 at 02:50:19PM +0000, Ryan Roberts wrote:
> Several CPUs implementing the BBML3 no-abort semantics advertise only
> BBML2, but cannot safely use those semantics because of hardware errata.
> Omitting their MIDRs from the allow list hides the reason for the
> exclusion and makes the relevant workarounds difficult to track.
>
> Add a default-enabled Kconfig option for each of the following errata,
> and include the affected CPUs in the BBML3 allow list only when the
> corresponding workaround is disabled:
>
> 3043240 Cortex-X925
> 3043263 Cortex-X4
> 3053180 Neoverse-V3 and Neoverse-V3AE
> 3683289 C1-Ultra and C1-Premium
> 3696239 Cortex-X3
> 3696242 Neoverse-V2
> 3696244 Cortex-A710 and Cortex-X2
> 3696250 Neoverse-N2
> 3696285 Neoverse-V1
> 4196850 C2-Ultra
I'm not sure what the benefit of this is. These CPUs are not listed in
the BBML3 capable list anyway, so the patch adds them but gated by a
Kconfig option, default y. Is it only an elaborate way to tell people
why we couldn't enable BBML3 support for them? Maybe the documentation
part is sufficient.
--
Catalin