[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bbf54737-ed49-5be8-722d-85906c803410@oracle.com>
Date: Mon, 31 Jul 2023 14:12:26 +0100
From: John Garry <john.g.garry@...cle.com>
To: Jing Zhang <renyu.zj@...ux.alibaba.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.
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.
Thanks,
John
Powered by blists - more mailing lists