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 6/6] arm64: cpufeature: Enable BBML3 on Cortex-A320, A520 and A720
Date: Wed, 18 Nov 2026 18:34:17 +0000 [thread overview]
Message-ID: <av3vqbBHGheAY06A@arm.com> (raw)
In-Reply-To: <20261113145022.2592454-7-ryan.roberts@arm.com>
On Fri, Nov 13, 2026 at 02:50:20PM +0000, Ryan Roberts wrote:
> Cortex-A320, Cortex-A520 and Cortex-A720 advertise BBML2 and are known
> not to raise conflict aborts for mapping-granularity changes. They can
> therefore use the BBML3 semantics, but their MIDRs are missing from the
> allow list.
>
> Commit a7ac60414475 ("arm64: cpufeature: Extend bbml2_noabort support
> list") named A520(AE) and A720(AE), but added only the AE MIDRs. The
> non-AE CPUs have distinct MIDRs and need their own entries. Cortex-A320
> can now be identified using its new MIDR definition.
>
> Add all revisions of these three CPUs to the allow list. The reviewed
> SDENs identify no BBML3 exclusion erratum for them.
>
> Cortex-A510 remains excluded because it can raise conflict aborts.
>
> Link: https://support.arm.com/documentation/SDEN-2877630/0000?lang=en&rev=0000-06
> Link: https://support.arm.com/documentation/SDEN-2444153/0000?lang=en&rev=0000-12
> Link: https://support.arm.com/documentation/SDEN-2439421/0000?lang=en&rev=0000-17
> Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2026-11-18 18:34 UTC|newest]
Thread overview: 11+ 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-18 18:33 ` Catalin Marinas
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
2026-11-13 14:50 ` [PATCH v1 6/6] arm64: cpufeature: Enable BBML3 on Cortex-A320, A520 and A720 Ryan Roberts
2026-11-18 18:34 ` Catalin Marinas [this message]
2026-11-18 18:27 ` (subset) [PATCH v1 0/6] arm64: BBML3 errata workarounds and cleanup Catalin Marinas
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=av3vqbBHGheAY06A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.