From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: mingo@redhat.com, ak@linux.intel.com,
Michael Ellerman <mpe@ellerman.id.au>,
Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, <linux-kernel@vger.kernel.org>
Subject: [RFC][PATCH 0/4] perf: Enable symbolic event names
Date: Fri, 1 May 2015 00:05:37 -0700 [thread overview]
Message-ID: <1430463941-26109-1-git-send-email-sukadev@linux.vnet.ibm.com> (raw)
Implement ability to specify Power PMU events by their symbolic event
names rather than raw codes. This approach pulls tables of the Power7
and Power8 PMU events into the perf source tree and uses these tables
to create aliases for the PMU events. With these aliases users can run:
perf stat -e PM_1PLUS_PPC_CMPL:ku sleep 1
or
perf stat -e cpu/PM_VSU_SINGLE/ sleep 1
This is an early POC patchset based on discussions with Jiri Olsa,
Michael Ellerman and Ingo Molnar. Lightly tested on Power7 and Power8.
Can other architectures can implement arch_get_events_table() and similarly
use symoblic event names?
I am also assuming that if the header files like power8-events.h are
easily readable, we don't need the JSON files anymore?
TODO:
- Maybe translate event names to lower-case?
- Allow perf to process event descriptions (need Andi Kleen's patch)
Sukadev Bhattiprolu (4):
perf: Create a table of Power7 PMU events
perf: Create a table of Power8 PMU events
perf/powerpc: Move mfspr and friends to header file
perf: Create aliases for Power PMU events
tools/perf/arch/powerpc/util/Build | 2 +-
tools/perf/arch/powerpc/util/header.c | 9 +-
tools/perf/arch/powerpc/util/header.h | 9 +
tools/perf/arch/powerpc/util/pmu-events.c | 52 +
tools/perf/arch/powerpc/util/pmu-events.h | 17 +
tools/perf/arch/powerpc/util/power7-events.h | 3315 +++++++++++++
tools/perf/arch/powerpc/util/power8-events.h | 6408 ++++++++++++++++++++++++++
tools/perf/util/pmu.c | 77 +
tools/perf/util/pmu.h | 10 +
9 files changed, 9890 insertions(+), 9 deletions(-)
create mode 100644 tools/perf/arch/powerpc/util/header.h
create mode 100644 tools/perf/arch/powerpc/util/pmu-events.c
create mode 100644 tools/perf/arch/powerpc/util/pmu-events.h
create mode 100644 tools/perf/arch/powerpc/util/power7-events.h
create mode 100644 tools/perf/arch/powerpc/util/power8-events.h
--
1.7.9.5
next reply other threads:[~2015-05-01 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 7:05 Sukadev Bhattiprolu [this message]
2015-05-01 7:05 ` [RFC][PATCH 1/4] perf: Create a table of Power7 PMU events Sukadev Bhattiprolu
2015-05-01 7:05 ` [RFC][PATCH 2/4] perf: Create a table of Power8 " Sukadev Bhattiprolu
2015-05-01 7:05 ` [RFC][PATCH 3/4] perf/powerpc: Move mfspr and friends to header file Sukadev Bhattiprolu
2015-05-01 7:05 ` [RFC][PATCH 4/4] perf: Create aliases for PMU events Sukadev Bhattiprolu
2015-05-02 7:04 ` Vineet Gupta
2015-05-02 15:38 ` Jiri Olsa
2015-05-04 11:44 ` Andi Kleen
2015-05-02 7:02 ` [RFC][PATCH 0/4] perf: Enable symbolic event names Vineet Gupta
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=1430463941-26109-1-git-send-email-sukadev@linux.vnet.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).