From: sashiko-bot@kernel.org
To: "Robin Murphy" <robin.murphy@arm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2] perf/arm_cspmu: Add Arm system PMU
Date: Mon, 05 Oct 2026 13:56:36 +0000 [thread overview]
Message-ID: <20261005135637.44FC31F000FF@smtp.kernel.org> (raw)
In-Reply-To: <162173d376d223941b0c8b4e4a1c9ad2ae5c11a3.1791207773.git.robin.murphy@arm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm_syspmu: build failure on 32-bit archs due to missing writeq fallback
--
commit ee9850d17fe1852cb671454c79f2ae56292d6550
Author: Robin Murphy <robin.murphy@arm.com>
perf/arm_cspmu: Add Arm system PMU
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.
> diff --git a/drivers/perf/arm_cspmu/arm_syspmu.c b/drivers/perf/arm_cspmu/arm_syspmu.c
> new file mode 100644
> index 0000000000000..ac234768a2f80
> --- /dev/null
> +++ b/drivers/perf/arm_cspmu/arm_syspmu.c
> @@ -0,0 +1,67 @@
[ ... ]
> +static void arm_syspmu_set_ev_filter(struct arm_cspmu *cspmu,
> + const struct perf_event *event)
> +{
> + u32 offset = 8 * event->hw.idx;
> +
> + writeq(event->attr.config1, cspmu->base0 + PMEVFILTR + offset);
> + writeq(event->attr.config2, cspmu->base0 + PMEVFILT2R + offset);
> + writeq(event->attr.config3, cspmu->base0 + PMEVFILT3R + offset);
[Severity: Low]
Will this driver fail to build on 32-bit architectures?
When compiling with CONFIG_COMPILE_TEST=y on a 32-bit platform like i386 or
ARM32, writeq() is not natively defined.
Could we include <linux/io-64-nonatomic-lo-hi.h> to ensure the driver
compiles successfully by providing a writeq() fallback for 32-bit builds?
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/162173d376d223941b0c8b4e4a1c9ad2ae5c11a3.1791207773.git.robin.murphy@arm.com?part=1
prev parent reply other threads:[~2026-10-05 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 13:42 [PATCH v2] perf/arm_cspmu: Add Arm system PMU Robin Murphy
2026-10-05 13:56 ` sashiko-bot [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=20261005135637.44FC31F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=sashiko-reviews@lists.linux.dev \
/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