From: Paul Clarke <pc@us.ibm.com>
To: linux-perf-users@vger.kernel.org
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
ananth@linux.vnet.ibm.com, maddy@linux.vnet.ibm.com,
naveen.n.rao@linux.vnet.ibm.com, sukadev@linux.ibm.com,
mpe@ellerman.id.au, cel@us.ibm.com
Subject: [PATCH v2 0/4] [powerpc] perf vendor events: Add JSON metrics for POWER9
Date: Sat, 9 Feb 2019 13:14:25 -0500 [thread overview]
Message-ID: <20190209181429.23950-1-pc@us.ibm.com> (raw)
[Note this is for POWER*9* and is different content than a
previous patchset for POWER*8*.]
The patches define metrics and metric groups for computation by "perf"
for POWER9 processors.
Paul Clarke (4):
[powerpc] perf vendor events: Add JSON metrics for POWER9
[powerpc] perf vendor events: Add JSON metrics for POWER9
[powerpc] perf vendor events: Add JSON metrics for POWER9
[powerpc] perf vendor events: Add JSON metrics for POWER9
v2:
The content of these patches was sent previously, to LKML and
linux-perf-users, but never showed up at linux-perf-users, so
I split it into smaller patches and am resending.
.../arch/powerpc/power9/metrics.json | 1982 +++++++++++++++++
1 file changed, 1982 insertions(+)
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/metrics.json
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Paul Clarke <pc@us.ibm.com>
To: linux-perf-users@vger.kernel.org
Cc: maddy@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, naveen.n.rao@linux.vnet.ibm.com,
sukadev@linux.ibm.com, cel@us.ibm.com
Subject: [PATCH v2 0/4] [powerpc] perf vendor events: Add JSON metrics for POWER9
Date: Sat, 9 Feb 2019 13:14:25 -0500 [thread overview]
Message-ID: <20190209181429.23950-1-pc@us.ibm.com> (raw)
[Note this is for POWER*9* and is different content than a
previous patchset for POWER*8*.]
The patches define metrics and metric groups for computation by "perf"
for POWER9 processors.
Paul Clarke (4):
[powerpc] perf vendor events: Add JSON metrics for POWER9
[powerpc] perf vendor events: Add JSON metrics for POWER9
[powerpc] perf vendor events: Add JSON metrics for POWER9
[powerpc] perf vendor events: Add JSON metrics for POWER9
v2:
The content of these patches was sent previously, to LKML and
linux-perf-users, but never showed up at linux-perf-users, so
I split it into smaller patches and am resending.
.../arch/powerpc/power9/metrics.json | 1982 +++++++++++++++++
1 file changed, 1982 insertions(+)
create mode 100644 tools/perf/pmu-events/arch/powerpc/power9/metrics.json
--
2.17.1
next reply other threads:[~2019-02-09 18:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 18:14 Paul Clarke [this message]
2019-02-09 18:14 ` [PATCH v2 0/4] [powerpc] perf vendor events: Add JSON metrics for POWER9 Paul Clarke
2019-02-09 18:14 ` [PATCH 1/4] " Paul Clarke
2019-02-09 18:14 ` Paul Clarke
2019-02-15 9:29 ` [tip:perf/core] perf vendor events power9: Cpi_breakdown & estimated_dcache_miss_cpi metrics tip-bot for Paul Clarke
2019-02-09 18:14 ` [PATCH 2/4] [powerpc] perf vendor events: Add JSON metrics for POWER9 Paul Clarke
2019-02-09 18:14 ` Paul Clarke
2019-02-15 9:30 ` [tip:perf/core] perf vendor events power9: Dl1_reloads, instruction_misses, l[23]_stats & pteg_reloads metrics tip-bot for Paul Clarke
2019-02-09 18:14 ` [PATCH 3/4] [powerpc] perf vendor events: Add JSON metrics for POWER9 Paul Clarke
2019-02-09 18:14 ` Paul Clarke
2019-02-15 9:31 ` [tip:perf/core] perf vendor events power9: Branch_prediction, instruction_stats, latency, lsu_rejects, memory, prefetch & translation metrics tip-bot for Paul Clarke
2019-02-09 18:14 ` [PATCH 4/4] [powerpc] perf vendor events: Add JSON metrics for POWER9 Paul Clarke
2019-02-09 18:14 ` Paul Clarke
2019-02-15 9:31 ` [tip:perf/core] perf vendor events power9: General metrics tip-bot for Paul Clarke
2019-02-11 15:53 ` [PATCH v2 0/4] [powerpc] perf vendor events: Add JSON metrics for POWER9 Arnaldo Carvalho de Melo
2019-02-11 15:53 ` 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=20190209181429.23950-1-pc@us.ibm.com \
--to=pc@us.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=cel@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=sukadev@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.