From: Beata Michalska <beata.michalska@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Vladimir.Murzin@arm.com, catalin.marinas@arm.com,
will@kernel.org, suzuki.poulose@arm.com, James.Morse@arm.com,
xuewen.yan94@gmail.com, seanwang1@lenovo.com,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/2] arm64: errata: Share broken AMU constant-counter handling
Date: Thu, 1 Oct 2026 11:00:30 +0200 [thread overview]
Message-ID: <20261001090050.3849551-1-beata.michalska@arm.com> (raw)
This series factors out the existing Cortex-A510 erratum 2457168 AMU constant
counter workaround into a generic broken AMU constant-counter capability,
then wires Cortex-A725 erratum 3821522 into the same handling.
---
v4:
- use midr range instead of multi cap list
- reword comment to be more generic
v3:
- splitted the commit and droped changes for cpucap_is_possible
---
Beata Michalska (2):
arm64: errata: Factor out broken AMU const counter cap
arm64: errata: Add Cortex-A725 erratum 3821522 workaround
Documentation/arch/arm64/silicon-errata.rst | 2 ++
arch/arm64/Kconfig | 30 +++++++++++++++++++++
arch/arm64/kernel/cpu_errata.c | 24 ++++++++++++-----
arch/arm64/kernel/cpufeature.c | 2 +-
arch/arm64/kernel/topology.c | 16 ++++++-----
arch/arm64/tools/cpucaps | 2 +-
6 files changed, 61 insertions(+), 15 deletions(-)
--
2.43.0
next reply other threads:[~2026-10-01 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 9:00 Beata Michalska [this message]
2026-10-01 9:00 ` [PATCH v4 1/2] arm64: errata: Factor out broken AMU const counter cap Beata Michalska
2026-10-01 12:10 ` Vladimir Murzin
2026-10-01 9:00 ` [PATCH v4 2/2] arm64: errata: Add Cortex-A725 erratum 3821522 workaround Beata Michalska
2026-10-01 12:12 ` Vladimir Murzin
2026-10-01 15:50 ` [PATCH v4 0/2] arm64: errata: Share broken AMU constant-counter handling 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=20261001090050.3849551-1-beata.michalska@arm.com \
--to=beata.michalska@arm.com \
--cc=James.Morse@arm.com \
--cc=Vladimir.Murzin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanwang1@lenovo.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=xuewen.yan94@gmail.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