Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Linu Cherian <linu.cherian@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 5/6] arm64: cpufeature: Track BBML3 exclusions with erratum options
Date: Wed, 18 Nov 2026 17:59:22 +0000	[thread overview]
Message-ID: <av3neu-9VTv8RgeY@arm.com> (raw)
In-Reply-To: <20261113145022.2592454-6-ryan.roberts@arm.com>

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


  reply	other threads:[~2026-11-18 17:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 14:50 [PATCH v1 0/6] arm64: BBML3 errata workarounds and cleanup Ryan Roberts
2026-11-13 14:50 ` [PATCH v1 1/6] arm64: cpufeature: Remove Neoverse-V3/AE from the BBML3 allow list Ryan Roberts
2026-11-13 14:50 ` [PATCH v1 2/6] arm64: cpufeature: Remove Cortex-X4 " Ryan Roberts
2026-11-13 14:50 ` [PATCH v1 3/6] arm64: cputype: Add Cortex-A320 definitions Ryan Roberts
2026-11-13 14:50 ` [PATCH v1 4/6] arm64: cputype: Add C2-Ultra definitions Ryan Roberts
2026-11-13 14:50 ` [PATCH v1 5/6] arm64: cpufeature: Track BBML3 exclusions with erratum options Ryan Roberts
2026-11-18 17:59   ` Catalin Marinas [this message]
2026-11-13 14:50 ` [PATCH v1 6/6] arm64: cpufeature: Enable BBML3 on Cortex-A320, A520 and A720 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=av3neu-9VTv8RgeY@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linu.cherian@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ryan.roberts@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