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] perf/arm_cspmu: Add Arm system PMU
Date: Mon, 5 Oct 2026 13:29:22 +0100 [thread overview]
Message-ID: <a44431a4-7a4e-4dea-b313-e769ecd55fad@arm.com> (raw)
In-Reply-To: <asKMMAvyAbT5mGJd@willie-the-truck>
On 04/10/2026 6:26 pm, Will Deacon wrote:
> On Wed, Sep 09, 2026 at 05:23:00PM +0100, Robin Murphy wrote:
>> Arm's latest Compute Subsystems and SoCs are using a common PMU block
>> in various places which can mostly just be driven as a generic 64-bit
>> CoreSight PMU, but does have an IMP-DEF register for additional
>> filtering. The details of event and filter encodings depend on the
>> particular PMU instance, so are left to the higher level Arm Telemetry
>> Solution tooling.
>>
>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>> ---
>> drivers/perf/arm_cspmu/Kconfig | 7 +++
>> drivers/perf/arm_cspmu/Makefile | 1 +
>> drivers/perf/arm_cspmu/arm_cspmu.c | 7 +++
>> drivers/perf/arm_cspmu/arm_cspmu.h | 1 +
>> drivers/perf/arm_cspmu/arm_syspmu.c | 67 +++++++++++++++++++++++++++++
>> 5 files changed, 83 insertions(+)
>> create mode 100644 drivers/perf/arm_cspmu/arm_syspmu.c
>
> Sashiko failed to apply this and so did I :/
>
> What is it based on?
Ah, sorry, I sent this straight off my local branch where it's on top of
the BMU patches - clearly I forgot to consider that that would mean some
context conflicts in the Kconfig and Makefile. I can resend if that's
easiest.
Cheers,
Robin.
prev parent reply other threads:[~2026-10-05 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 16:23 [PATCH] perf/arm_cspmu: Add Arm system PMU Robin Murphy
2026-10-04 17:26 ` Will Deacon
2026-10-05 12:29 ` 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=a44431a4-7a4e-4dea-b313-e769ecd55fad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox