From: Robin Murphy <robin.murphy@arm.com>
To: Will Deacon <will@kernel.org>
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: Mon, 5 Oct 2026 14:15:32 +0100 [thread overview]
Message-ID: <426110f0-0ef4-4f15-b68f-103a863df3aa@arm.com> (raw)
In-Reply-To: <asLO8rGQPYo3KhKB@willie-the-truck>
On 04/10/2026 11:10 pm, Will Deacon wrote:
> 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?
I did start writing a reply at the time, but it was getting so sarcastic
that even I thought better of sending it...
In (polite) summary:
1 - Gibberish
2 - Yes if firmware blatantly mis-describes the hardware then Linux may
not work properly. Whoop de do.
3 - Yeah so?
4 - Pants-on-head gibberish, but the second part about COMPILE_TEST is
fair (an oversight from ripping out the DT support) - fix is already in
-next via the ACPI tree[1]
5 - Yeah so?
6,7 - Yes, welcome to perf...
Cheers,
Robin.
[1]
https://lore.kernel.org/all/CAJZ5v0g4k6FhyQMypkRyVJMkSBUsmeuetJuxRA826PcA7Mo5Hg@mail.gmail.com/
prev parent reply other threads:[~2026-10-05 13:15 UTC|newest]
Thread overview: 4+ 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-09-17 14:02 ` sashiko-bot
2026-10-04 22:10 ` Will Deacon
2026-10-05 13:15 ` Robin Murphy [this message]
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=426110f0-0ef4-4f15-b68f-103a863df3aa@arm.com \
--to=robin.murphy@arm.com \
--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 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.