From: Jin Yao <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com,
rickyman7@gmail.com, Jin Yao <yao.jin@linux.intel.com>
Subject: [PATCH v4 0/2] perf tools: Add PMU alias support
Date: Wed, 11 Aug 2021 10:48:25 +0800 [thread overview]
Message-ID: <20210811024827.9483-1-yao.jin@linux.intel.com> (raw)
A perf uncore PMU may have two PMU names, a real name and an alias name.
With this patch set, the perf tool can monitor the PMU with either the
real name or the alias.
Use the real name,
$ perf stat -e uncore_cha_2/event=1/ -x,
4044879584,,uncore_cha_2/event=1/,2528059205,100.00,,
Use the alias,
$ perf stat -e uncore_type_0_2/event=1/ -x,
3659675336,,uncore_type_0_2/event=1/,2287306455,100.00,,
v4:
---
1. Fix memory leaks in pmu_lookup.
2. Rebase to perf/core.
v3:
---
1. Use fgets() to replace fscanf().
2. Resource cleanup.
v2:
---
Add test case to verify the real name and alias name having same effect.
Jin Yao (1):
perf tests: Test for PMU alias
Kan Liang (1):
perf pmu: Add PMU alias support
tools/perf/arch/x86/util/pmu.c | 129 +++++++++++++++++++++++++++++++-
tools/perf/tests/parse-events.c | 92 +++++++++++++++++++++++
tools/perf/util/parse-events.y | 3 +-
tools/perf/util/pmu.c | 47 +++++++++---
tools/perf/util/pmu.h | 5 ++
5 files changed, 264 insertions(+), 12 deletions(-)
--
2.17.1
next reply other threads:[~2021-08-11 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 2:48 Jin Yao [this message]
2021-08-11 2:48 ` [PATCH v4 1/2] perf pmu: Add PMU alias support Jin Yao
2021-08-11 13:27 ` Andi Kleen
2021-08-12 4:39 ` Jin, Yao
2021-08-11 19:23 ` Jiri Olsa
2021-08-12 4:32 ` Jin, Yao
2021-08-12 12:14 ` John Garry
2021-08-13 1:59 ` Jin, Yao
2021-08-11 2:48 ` [PATCH v4 2/2] perf tests: Test for PMU alias Jin Yao
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=20210811024827.9483-1-yao.jin@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rickyman7@gmail.com \
--cc=yao.jin@intel.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;
as well as URLs for NNTP newsgroup(s).