From: Andi Kleen <andi@firstfloor.org>
To: acme@kernel.org
Cc: jolsa@kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: [PATCH 05/11] perf, tools: Support per pmu json aliases
Date: Tue, 18 Oct 2016 16:07:43 -0700 [thread overview]
Message-ID: <1476832069-364-6-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1476832069-364-1-git-send-email-andi@firstfloor.org>
From: Andi Kleen <ak@linux.intel.com>
Add support for registering json aliases per PMU. Any alias
with an unit matching the prefix is registered to the PMU.
Uncore has multiple instances of most units, so all
these aliases get registered for each individual PMU
(this is important later to run the event on every instance
of the PMU).
To avoid printing the events multiple times in perf list
filter out duplicated events during printing.
v2: Rely on uncore_ prefix already in unit
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
tools/perf/util/pmu.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
index 6edcba323543..5b114f18919b 100644
--- a/tools/perf/util/pmu.c
+++ b/tools/perf/util/pmu.c
@@ -587,14 +587,13 @@ static struct perf_pmu *pmu_lookup(const char *name)
if (pmu_format(name, &format))
return NULL;
- if (pmu_aliases(name, &aliases))
+ if (pmu_type(name, &type))
return NULL;
- pmu_add_cpu_aliases(&aliases, name);
-
- if (pmu_type(name, &type))
+ if (pmu_aliases(name, &aliases))
return NULL;
+ pmu_add_cpu_aliases(&aliases, name);
pmu = zalloc(sizeof(*pmu));
if (!pmu)
return NULL;
@@ -1190,6 +1189,9 @@ void print_pmu_events(const char *event_glob, bool name_only, bool quiet_flag,
len = j;
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))
+ continue;
if (name_only) {
printf("%s ", aliases[j].name);
continue;
--
2.5.5
next prev parent reply other threads:[~2016-10-18 23:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 23:07 Support Intel uncore event lists v2 Andi Kleen
2016-10-18 23:07 ` [PATCH 01/11] perf, tools: Factor out scale conversion code Andi Kleen
2016-10-18 23:07 ` [PATCH 02/11] perf, tools: Only print Using CPUID message once Andi Kleen
2016-10-18 23:07 ` [PATCH 03/11] perf, tools: Parse eventcode as number in jevents Andi Kleen
2016-10-18 23:07 ` [PATCH 04/11] perf, tools: Add support for parsing uncore json files Andi Kleen
2016-10-18 23:07 ` Andi Kleen [this message]
2016-10-18 23:07 ` [PATCH 06/11] perf, tools: Support event aliases for non cpu// pmus Andi Kleen
2016-10-18 23:07 ` [PATCH 07/11] perf, tools: Add debug support for outputing alias string Andi Kleen
2016-10-18 23:07 ` [PATCH 08/11] perf, tools: Collapse identically named events in perf stat Andi Kleen
2016-10-18 23:07 ` [PATCH 09/11] perf, tools: Expand PMU events by prefix match Andi Kleen
2016-10-18 23:07 ` [PATCH 10/11] perf, tools: Support DividedBy header in JSON event list Andi Kleen
2016-10-18 23:07 ` [PATCH 11/11] perf, tools, stat: Output generic dividedby metric Andi Kleen
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=1476832069-364-6-git-send-email-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.