From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Anton Blanchard <anton@au1.ibm.com>, Jiri Olsa <jolsa@redhat.com>,
mpetlan@redhat.com, Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [GIT PULL] Please pull JSON files for POWER9 PMU events
Date: Thu, 31 Aug 2017 13:38:33 -0300 [thread overview]
Message-ID: <20170831163833.GG4831@kernel.org> (raw)
In-Reply-To: <20170830231506.GB20351@us.ibm.com>
Em Wed, Aug 30, 2017 at 04:15:06PM -0700, Sukadev Bhattiprolu escreveu:
>
> Hi Arnaldo,
>
> Please pull an update to the JSON files for POWER9 PMU events. This
> removes alternate event codes from the JSON files which seem to confuse
> perf.
>
> The following changes since commit 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9:
Thanks, applied and added the CCed people to CC lines in the cset
comment, also added Andi to that CC list.
- Arnaldo
> Merge tag 'perf-core-for-mingo-4.14-20170829' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core (2017-08-29 23:13:56 +0200)
>
> are available in the git repository at:
>
> https://github.com/sukadev/linux/ p9-json-v3
>
> Sukadev Bhattiprolu (1):
> perf vendor events powerpc: remove duplicate events
>
> .../pmu-events/arch/powerpc/power9/frontend.json | 7 +-
> .../perf/pmu-events/arch/powerpc/power9/other.json | 120 --------------------
> .../pmu-events/arch/powerpc/power9/pipeline.json | 7 +-
> tools/perf/pmu-events/arch/powerpc/power9/pmc.json | 7 +-
> 4 files changed, 3 insertions(+), 138 deletions(-)
next prev parent reply other threads:[~2017-08-31 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 23:15 [GIT PULL] Please pull JSON files for POWER9 PMU events Sukadev Bhattiprolu
2017-08-31 16:38 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-02 17:46 [GIT PULL] Please pull JSON files for Power9 " Sukadev Bhattiprolu
2017-08-02 18:35 ` Arnaldo Carvalho de Melo
2017-07-12 2:08 Sukadev Bhattiprolu
2017-07-12 12:09 ` 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
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=20170831163833.GG4831@kernel.org \
--to=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=anton@au1.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=mpetlan@redhat.com \
--cc=sukadev@linux.vnet.ibm.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).