From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org, mark.rutland@arm.com
Cc: devicetree@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] perf: Support Arm Bus Monitor Unit
Date: Thu, 16 Jul 2026 16:12:38 +0100 [thread overview]
Message-ID: <cover.1784214112.git.robin.murphy@arm.com> (raw)
Hi all,
Here we have the delight of another new PMU driver. While not am Arm
product in its own right, the BMU is found in the latest Neoverse
Compute Subsystems, including the recently-announced AGI CPU.
For now it is expected that BMU users will be ACPI-based (binding in
the latest "ACPI for Arm Components" release[1]), so the token DT
binding is more for completeness and maybe very early bringup hacking.
I've kept it here for the sake of discussion, but the only requirement
on me for now is to get patch #1 landed.
And yes, I did initially look at trying to factor out the PMU register
accesses that functionally overlap the existing arm_cspmu code, but it
very quickly became clear that that would end up far bigger and more
complex. This is not a big driver, even with a few dozen lines of
nominally-duplicate (but also simplified since the counter size etc.
is fixed and known) code, so this way it went.
v1: https://lore.kernel.org/linux-perf-users/cover.1783439341.git.robin.murphy@arm.com/
v2: Fix valid Sashiko nits, separate DT support
Thanks,
Robin.
[1] https://developer.arm.com/documentation/den0093/latest/
Robin Murphy (3):
perf: Add Arm Bus Monitor Unit driver
dt-bindings: perf: Add Arm Bus Monitor Unit
perf/arm-bmu: Add Devicetree support
.../bindings/perf/arm,bus-monitor-unit.yaml | 41 ++
drivers/perf/arm_cspmu/Kconfig | 6 +
drivers/perf/arm_cspmu/Makefile | 2 +
drivers/perf/arm_cspmu/arm-bmu.c | 538 ++++++++++++++++++
4 files changed, 587 insertions(+)
create mode 100644 Documentation/devicetree/bindings/perf/arm,bus-monitor-unit.yaml
create mode 100644 drivers/perf/arm_cspmu/arm-bmu.c
--
2.54.0.dirty
next reply other threads:[~2026-07-16 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 15:12 Robin Murphy [this message]
2026-07-16 15:12 ` [PATCH v2 1/3] perf: Add Arm Bus Monitor Unit driver Robin Murphy
2026-07-16 15:31 ` sashiko-bot
2026-07-16 15:12 ` [PATCH v2 2/3] dt-bindings: perf: Add Arm Bus Monitor Unit Robin Murphy
2026-07-16 15:24 ` sashiko-bot
2026-07-16 15:12 ` [PATCH v2 3/3] perf/arm-bmu: Add Devicetree support Robin Murphy
2026-07-16 15:26 ` sashiko-bot
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=cover.1784214112.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@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