From: Michael Ellerman <mpe@ellerman.id.au>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
ak@linux.intel.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, mikey@neuling.org,
mpetlan@redhat.com
Subject: Re: [GIT PULL] Please pull JSON files for Power9 PMU events
Date: Thu, 13 Jul 2017 13:43:41 +1000 [thread overview]
Message-ID: <87y3rtj91u.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170712164008.GC31223@us.ibm.com>
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com> writes:
...
>
> tools/perf/pmu-events/arch/powerpc/mapfile.csv | 3 +
> .../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 ++++
In the map file we have "power9.json", but the files are power9/x.json.
How does that work?
cheers
next prev parent reply other threads:[~2017-07-13 3:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2017-07-13 8:09 ` Jiri Olsa
2017-07-13 9:50 ` Michael Ellerman
2017-07-13 3:42 ` Michael Ellerman
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=87y3rtj91u.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--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
all inboxes | Powered by JetHome®