From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
Andi Kleen <andi@firstfloor.orgi>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull JSON files for Power9 PMU events
Date: Tue, 11 Jul 2017 19:08:27 -0700 [thread overview]
Message-ID: <20170712020827.GB31223@us.ibm.com> (raw)
Hi Arnaldo,
Please pull the JSON files for POWER9 PMU events.
The following changes since commit 07d306c838c5c30196619baae36107d0615e459b:
Merge git://www.linux-watchdog.org/linux-watchdog (2017-07-11 09:59:37 -0700)
are available in the git repository at:
https://github.com/sukadev/linux/ p9-json
for you to fetch changes up to f94a86dbb13e18bd7ad566cabe42df63d3bd1039:
perf vendor events: Add POWER9 PVRs to mapfile (2017-07-11 19:30:40 -0500)
----------------------------------------------------------------
Sukadev Bhattiprolu (2):
perf vendor events: Add POWER9 PMU events
perf vendor events: Add POWER9 PVRs to mapfile
tools/perf/pmu-events/arch/powerpc/mapfile.csv | 2 +
.../perf/pmu-events/arch/powerpc/power9/cache.json | 176 +++++
.../arch/powerpc/power9/floating-point.json | 44 ++
.../pmu-events/arch/powerpc/power9/frontend.json | 446 +++++++++++
.../pmu-events/arch/powerpc/power9/marked.json | 782 +++++++++++++++++++
.../pmu-events/arch/powerpc/power9/memory.json | 158 ++++
.../perf/pmu-events/arch/powerpc/power9/other.json | 836 +++++++++++++++++++++
.../pmu-events/arch/powerpc/power9/pipeline.json | 680 +++++++++++++++++
tools/perf/pmu-events/arch/powerpc/power9/pmc.json | 146 ++++
.../arch/powerpc/power9/translation.json | 272 +++++++
10 files changed, 3542 insertions(+)
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/cache.json
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/floating-point.json
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/frontend.json
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/marked.json
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/memory.json
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/other.json
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/pipeline.json
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/pmc.json
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/translation.json
next reply other threads:[~2017-07-12 2:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 2:08 Sukadev Bhattiprolu [this message]
2017-07-12 12:09 ` [GIT PULL] Please pull JSON files for Power9 PMU events Michael Ellerman
2017-07-12 14:46 ` Arnaldo Carvalho de Melo
2017-07-12 16:40 ` Sukadev Bhattiprolu
2017-07-12 19:49 ` Arnaldo Carvalho de Melo
2017-07-13 3:43 ` Michael Ellerman
2017-07-13 8:09 ` Jiri Olsa
2017-07-13 9:50 ` Michael Ellerman
2017-07-13 3:42 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2017-08-02 17:46 Sukadev Bhattiprolu
2017-08-02 18:35 ` Arnaldo Carvalho de Melo
2017-08-30 23:15 [GIT PULL] Please pull JSON files for POWER9 " Sukadev Bhattiprolu
2017-08-31 16:38 ` Arnaldo Carvalho de Melo
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=20170712020827.GB31223@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.orgi \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
/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).