From: Jiri Olsa <jolsa@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, irogers@google.com,
kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf pmu: Fix event list for uncore PMUs
Date: Tue, 21 Dec 2021 08:58:31 +0100 [thread overview]
Message-ID: <YcGJJ2g+i5qWea7d@krava> (raw)
In-Reply-To: <1639670017-74918-1-git-send-email-john.garry@huawei.com>
On Thu, Dec 16, 2021 at 11:53:37PM +0800, John Garry wrote:
> Commit 0e0ae8742207 ("perf list: Display hybrid PMU events with cpu type")
> changed the list for uncore PMUs, such that duplicate aliases are now
> listed per PMU (which they should not be), like:
>
> ./perf list
> ...
> unc_cbo_cache_lookup.any_es
> [Unit: uncore_cbox L3 Lookup any request that access cache and found
> line in E or S-state]
> unc_cbo_cache_lookup.any_es
> [Unit: uncore_cbox L3 Lookup any request that access cache and found
> line in E or S-state]
> unc_cbo_cache_lookup.any_i
> [Unit: uncore_cbox L3 Lookup any request that access cache and found
> line in I-state]
> unc_cbo_cache_lookup.any_i
> [Unit: uncore_cbox L3 Lookup any request that access cache and found
> line in I-state]
> ...
>
> Notice how the events are listed twice.
>
> The named commit changed how we remove duplicate events, in that events
> for different PMUs are not treated as duplicates. I suppose this is to
> handle how "Each hybrid pmu event has been assigned with a pmu name".
>
> Fix uncore PMU alias list by also checking if events with PMU name are not
> cpu PMUs.
>
> Fixes: 0e0ae8742207 ("perf list: Display hybrid PMU events with cpu type")
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
> It would be helpful if someone with some of these hybrid CPU systems could
> test this change, thanks!
>
> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> index 6ae58406f4fc..392f6a36418b 100644
> --- a/tools/perf/util/pmu.c
> +++ b/tools/perf/util/pmu.c
> @@ -1659,6 +1659,24 @@ bool is_pmu_core(const char *name)
> return !strcmp(name, "cpu") || is_arm_pmu_core(name);
> }
>
> +static bool pmu_alias_is_duplicate(struct sevent *alias_a,
> + struct sevent *alias_b)
> +{
> + /* Different names -> never duplicates */
> + if (strcmp(alias_a->name, alias_b->name))
> + return false;
> + if (!alias_a->pmu)
> + return true;
> + if (!alias_b->pmu)
> + return true;
nit could be:
if (!alias_a->pmu || !alias_b->pmu)
return true;
would be great to have more comments explaining the check
thanks,
jirka
> + if (!strcmp(alias_a->pmu, alias_b->pmu))
> + return true;
> + /* uncore PMUs */
> + if (!alias_a->is_cpu && !alias_b->is_cpu)
> + return true;
> + return false;
> +}
> +
> void print_pmu_events(const char *event_glob, bool name_only, bool quiet_flag,
> bool long_desc, bool details_flag, bool deprecated,
> const char *pmu_name)
> @@ -1744,12 +1762,8 @@ void print_pmu_events(const char *event_glob, bool name_only, bool quiet_flag,
> qsort(aliases, len, sizeof(struct sevent), cmp_sevent);
> for (j = 0; j < len; j++) {
> /* Skip duplicates */
> - if (j > 0 && !strcmp(aliases[j].name, aliases[j - 1].name)) {
> - if (!aliases[j].pmu || !aliases[j - 1].pmu ||
> - !strcmp(aliases[j].pmu, aliases[j - 1].pmu)) {
> - continue;
> - }
> - }
> + if (j > 0 && pmu_alias_is_duplicate(&aliases[j], &aliases[j - 1]))
> + continue;
>
> if (name_only) {
> printf("%s ", aliases[j].name);
> --
> 2.26.2
>
next prev parent reply other threads:[~2021-12-21 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 15:53 [PATCH] perf pmu: Fix event list for uncore PMUs John Garry
2021-12-18 1:47 ` Arnaldo Carvalho de Melo
2021-12-20 8:38 ` John Garry
2021-12-20 16:34 ` Liang, Kan
2021-12-21 6:59 ` Xing Zhengjun
2021-12-21 7:58 ` Jiri Olsa [this message]
2021-12-21 9:10 ` John Garry
2021-12-21 9:35 ` Jiri Olsa
2021-12-21 10:14 ` John Garry
2021-12-21 20:48 ` Arnaldo Carvalho de Melo
2021-12-22 13:08 ` John Garry
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=YcGJJ2g+i5qWea7d@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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