From: Robin Murphy <robin.murphy@arm.com>
To: "allen.wang" <allen.wang@hj-micro.com>, will@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
peter.du@hj-micro.com, andy.xu@hj-micro.com
Subject: Re: [PATCH] perf/arm-cmn: Fix {wp_dev_sel2, wp_dev_sel} limited to 0/1 when MXP_MULTIPLE_DTM_EN is TRUE
Date: Tue, 8 Sep 2026 16:04:57 +0100 [thread overview]
Message-ID: <58adffd2-6ef4-4a4c-ba3a-3f510522d928@arm.com> (raw)
In-Reply-To: <f97fa5ae-3535-4e1a-a164-77138a93cc89@hj-micro.com>
On 08/09/2026 9:15 am, allen.wang wrote:
> Hi,
>
> Gentle ping on this patch.
>
> Could someone please review it when time permits?
>
> Thanks!
> Allen
>
> On 8/19/2026 6:54 PM, Shouping Wang wrote:
>> When MXP_MULTIPLE_DTM_EN is TRUE, each DTM will monitor at most
>> two device ports. In this case, {wp_dev_sel2, wp_dev_sel} will
>> only use values 2'b00 and 2'b01 per DTM.
Hmm, I read the "each DTM will only use..." wording[1] as implying that
the hardware itself would ignore wp_dev_sel2 (especially since that
would seem to be the obvious thing to do) - are you saying that that
isn't the case? (I've never had access to any actual multi-DTM hardware...)
Thanks,
Robin.
[1]
https://support.arm.com/documentation/102308/0307/Debug-trace-and-PMU/Debug-Trace-system-overview/DTM-watchpoint?lang=en
>> Previously the setting allowed values beyond the supported range
>> per DTM, which could cause each DTM to select invalid ports when
>> MXP_MULTIPLE_DTM_EN is TRUE.
>>
>> Fix this by applying `dev %= 2` to clamp the selection value to
>> the valid range when MXP_MULTIPLE_DTM_EN is TRUE.
>>
>> Fixes: 60d1504070c2 ("perf/arm-cmn: Support new IP features")
>> Signed-off-by: Shouping Wang <allen.wang@hj-micro.com>
>> ---
>> drivers/perf/arm-cmn.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/perf/arm-cmn.c b/drivers/perf/arm-cmn.c
>> index 40c05c519a1d..13ccbf2a7345 100644
>> --- a/drivers/perf/arm-cmn.c
>> +++ b/drivers/perf/arm-cmn.c
>> @@ -1392,6 +1392,7 @@ static void arm_cmn_claim_wp_idx(struct arm_cmn_dtm *dtm,
>>
>> static u32 arm_cmn_wp_config(struct perf_event *event, int wp_idx)
>> {
>> + struct arm_cmn *cmn = to_cmn(event->pmu);
>> u32 config;
>> u32 dev = CMN_EVENT_WP_DEV_SEL(event);
>> u32 chn = CMN_EVENT_WP_CHN_SEL(event);
>> @@ -1404,6 +1405,9 @@ static u32 arm_cmn_wp_config(struct perf_event *event, int wp_idx)
>> if (is_cmn600)
>> grp &= 1;
>>
>> + if (cmn->multi_dtm)
>> + dev %= 2;
>> +
>> config = FIELD_PREP(CMN_DTM_WPn_CONFIG_WP_DEV_SEL, dev) |
>> FIELD_PREP(CMN_DTM_WPn_CONFIG_WP_CHN_SEL, chn) |
>> FIELD_PREP(CMN_DTM_WPn_CONFIG_WP_GRP, grp) |
>
next prev parent reply other threads:[~2026-09-08 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:54 Shouping Wang
2026-09-08 8:15 ` allen.wang
2026-09-08 15:04 ` Robin Murphy [this message]
2026-09-09 2:01 ` allen.wang
2026-09-09 16:19 ` Robin Murphy
2026-09-10 11:46 ` [PATCH v2] perf/arm-cmn: Fix wp_dev_sel2 setting for multi-DTM configurations Shouping Wang
2026-09-10 12:37 ` Robin Murphy
2026-09-11 13:44 ` Will Deacon
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=58adffd2-6ef4-4a4c-ba3a-3f510522d928@arm.com \
--to=robin.murphy@arm.com \
--cc=allen.wang@hj-micro.com \
--cc=andy.xu@hj-micro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peter.du@hj-micro.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
all inboxes | Powered by JetHome®