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>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull JSON files for POWR9 PMU events
Date: Wed, 8 Nov 2017 12:19:38 -0800 [thread overview]
Message-ID: <20171108201938.GA10985@us.ibm.com> (raw)
Hi Arnaldo,
Please pull an update to the JSON files for POWER9 PMU events.
The following changes since commit 148b43a3540bf25875bb5ab695a446950dc8d559:
tools headers: Synchronize kernel ABI headers wrt SPDX tags (2017-11-07 13:41:35 -0300)
are available in the git repository at:
https://github.com/sukadev/linux p9-json-v4
for you to fetch changes up to 4afb062d7d306bf56dbae9b5291e3515ccfede4c:
perf vendor events powerpc: Update POWER9 events (2017-11-08 18:42:03 -0500)
----------------------------------------------------------------
Sukadev Bhattiprolu (1):
perf vendor events powerpc: Update POWER9 events
.../perf/pmu-events/arch/powerpc/power9/cache.json | 5 -
.../pmu-events/arch/powerpc/power9/frontend.json | 7 +-
.../pmu-events/arch/powerpc/power9/marked.json | 27 +-
.../perf/pmu-events/arch/powerpc/power9/other.json | 276 ++++++---------------
.../pmu-events/arch/powerpc/power9/pipeline.json | 14 +-
tools/perf/pmu-events/arch/powerpc/power9/pmc.json | 2 +-
.../arch/powerpc/power9/translation.json | 5 -
7 files changed, 88 insertions(+), 248 deletions(-)
next reply other threads:[~2017-11-08 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 20:19 Sukadev Bhattiprolu [this message]
2017-11-09 19:15 ` [GIT PULL] Please pull JSON files for POWR9 PMU events Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2018-03-13 22:46 Sukadev Bhattiprolu
2018-03-14 20:41 ` 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=20171108201938.GA10985@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--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).