From: Jing Zhang <renyu.zj@linux.alibaba.com>
To: "Liang, Kan" <kan.liang@linux.intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Shuai Xue <xueshuai@linux.alibaba.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/x86/intel/uncore: Fix the lack of ch_mask format for SPR
Date: Mon, 6 Jan 2025 10:16:34 +0800 [thread overview]
Message-ID: <9f233d6e-ee4b-4ea3-96ee-397bba1b73b0@linux.alibaba.com> (raw)
In-Reply-To: <7e5376f1-ee87-458b-b55e-759125d251a2@linux.intel.com>
在 2025/1/3 上午3:02, Liang, Kan 写道:
>
>
> On 2024-12-30 2:11 a.m., Jing Zhang wrote:
>> perf stat errors out with UNC_CHA_TOR_INSERTS.IA_HIT_CXL_ACC_LOCAL event
>> because of lack of ch_mask format in drivers, and perf test "104: perf
>> all PMU test (exclusive)" failed.
>>
>> $perf stat -e perf stat -e UNC_CHA_TOR_INSERTS.IA_HIT_CXL_ACC_LOCAL
>> sleep 1
>>
>> Initial error:
>> event syntax error: 'UNC_CHA_TOR_INSERTS.IA_HIT_CXL_ACC_LOCAL'
>> \___ unknown term 'ch_mask' for pmu 'uncore_cha_0'
>>
>> 104: perf all PMU test (exclusive) : FAILED!
>>
>> Add ch_mask format for SPR to fix it.
>>
>
> I don't think there is a ch_mask. It should be extended umask.
> The issue of the CHA extended umask should has been fixed by
> https://lore.kernel.org/lkml/172052531679.2215.16140288595428337453.tip-bot2@tip-bot2/
>
I think it is not the same issue. I have this patch but still error.
in "tools/perf/pmu-events/arch/x86/sapphirerapids/uncore-cache.json",
the event "UNC_CHA_TOR_INSERTS.IA_HIT_CXL_ACC_LOCAL" is described as:
{
"BriefDescription": "UNC_CHA_TOR_INSERTS.IA_HIT_CXL_ACC_LOCAL",
"Counter": "0,1,2,3",
"EventCode": "0x35",
"EventName": "UNC_CHA_TOR_INSERTS.IA_HIT_CXL_ACC_LOCAL",
"Experimental": "1",
"PerPkg": "1",
"PortMask": "0x000",
"UMask": "0x10c0008101",
"Unit": "CHA"
},
the PortMask is ch_mask, but driver not output ch_mask on SPR, it causes error.
Thanks,
Jing
> Thanks,
> Kan
>> Fixes: 949b11381f81 ("perf/x86/intel/uncore: Add Sapphire Rapids server CHA support")
>> Signed-off-by: Jing Zhang <renyu.zj@linux.alibaba.com>
>> ---
>> arch/x86/events/intel/uncore_snbep.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/x86/events/intel/uncore_snbep.c b/arch/x86/events/intel/uncore_snbep.c
>> index ca98744..e537623 100644
>> --- a/arch/x86/events/intel/uncore_snbep.c
>> +++ b/arch/x86/events/intel/uncore_snbep.c
>> @@ -5967,6 +5967,7 @@ static int spr_cha_hw_config(struct intel_uncore_box *box, struct perf_event *ev
>> &format_attr_inv.attr,
>> &format_attr_thresh8.attr,
>> &format_attr_filter_tid5.attr,
>> + &format_attr_ch_mask.attr,
>> NULL,
>> };
>> static const struct attribute_group spr_uncore_chabox_format_group = {
next prev parent reply other threads:[~2025-01-06 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 7:11 Jing Zhang
2025-01-02 19:02 ` Liang, Kan
2025-01-06 2:16 ` Jing Zhang [this message]
2025-01-06 13:44 ` Liang, Kan
2025-01-07 1:55 ` Jing Zhang
2025-01-07 17:12 ` Falcon, Thomas
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=9f233d6e-ee4b-4ea3-96ee-397bba1b73b0@linux.alibaba.com \
--to=renyu.zj@linux.alibaba.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=xueshuai@linux.alibaba.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
all inboxes | Powered by JetHome®