From: Will Deacon <will@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: mark.rutland@arm.com, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] perf: Add Arm Bus Monitor Unit driver
Date: Sun, 4 Oct 2026 23:10:58 +0100 [thread overview]
Message-ID: <asLO8rGQPYo3KhKB@willie-the-truck> (raw)
In-Reply-To: <c936505c43275f434bce924b7657e42bfb25579c.1789652832.git.robin.murphy@arm.com>
On Thu, Sep 17, 2026 at 02:47:12PM +0100, Robin Murphy wrote:
> Arm's Bus Monitor Unit is a low-level performance analysis tool for
> matching and counting transactions at interconnect interfaces. Each
> BMU consists of a number of "interface monitoring units", with some
> global controls to synchronise them and so permit accurate calculation
> of cross-interface metrics. Each IMU contains, among other things, its
> own PMU largely based on the CoreSight PMU architecture, but with some
> functional incompatibilities due to the nature of how much per-event
> filtering needs to be crammed in to categorise AXI/CHI transactions at
> the protocol level. As such it gets an honorary home in arm_cspmu/ in
> order to share the common register definitions, but for simplicity does
> not try to bend the functional abstraction to fit.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>
> ---
> v3:
> - Couple of inconsequential tweaks to shut Sashiko up about things
> that would never actually happen anyway
> - Drop unneeded DT patches that I can't be bothered to fix right now
Please can you take a look at the Sashiko comments on this one?
Will
next prev parent reply other threads:[~2026-10-04 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 13:47 [PATCH v3] perf: Add Arm Bus Monitor Unit driver Robin Murphy
2026-10-04 22:10 ` Will Deacon [this message]
2026-10-05 13:15 ` Robin Murphy
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=asLO8rGQPYo3KhKB@willie-the-truck \
--to=will@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.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