[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f863dcf3-d7a5-48f6-a07c-94f6f709c238@linux.alibaba.com>
Date: Tue, 1 Aug 2023 17:19:09 +0800
From: Jing Zhang <renyu.zj@...ux.alibaba.com>
To: John Garry <john.g.garry@...cle.com>,
Ian Rogers <irogers@...gle.com>
Cc: Will Deacon <will@...nel.org>, Mark Rutland <mark.rutland@....com>,
Robin Murphy <robin.murphy@....com>,
Ilkka Koskinen <ilkka@...amperecomputing.com>,
Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-perf-users@...r.kernel.org, linux-doc@...r.kernel.org,
Zhuo Song <zhuo.song@...ux.alibaba.com>,
Shuai Xue <xueshuai@...ux.alibaba.com>
Subject: Re: [PATCH v5 3/5] perf test: Add pmu-event test for "Compat" and new
event_field.
在 2023/7/31 下午9:12, John Garry 写道:
> On 31/07/2023 13:30, Jing Zhang wrote:
>>>> + .pmu = {
>>>> + .name = (char *)"uncore_arm_cmn_0",
>>>> + .is_uncore = 1,
>>>> + .id = (char *)"43602",
>>>> + },
>>>> + .aliases = {
>>>> + &sys_cmn_pmu_hnf_cache_miss,
>>>> + },
>>>> + },
>>>> + {
>>>> + .pmu = {
>>>> + .name = (char *)"uncore_arm_cmn_1",
>>> Shouldn't this match some perf_pmu_test_event entry with same matching_pmu member? But is perf_pmu_test_event.matching_pmu member ever used for any checking???
>>>
>> I need to double check because I was testing against 6.3-rc2.
>
> That 6.3-rc2, was for the the kernel? Or baseline for this series? See see maintainers for git/branch to base perf tool dev on.
>
I have now developed based on the latest perf tool, but I'm still confused.
"matching_pmu" does not seem to have any effect. No matter what value matching_pmu
is, it will not affect the final test result.
Thank,
Jing
Powered by blists - more mailing lists