From: tip-bot for Andi Kleen <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: jolsa@redhat.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, acme@redhat.com,
ak@linux.intel.com, hpa@zytor.com, mingo@kernel.org
Subject: [tip:perf/core] perf vendor events: Add JSON metrics for Haswell EP
Date: Fri, 22 Sep 2017 09:40:46 -0700 [thread overview]
Message-ID: <tip-5e49f7321b06428ac68c51096cff9a4a55c3d4d6@git.kernel.org> (raw)
In-Reply-To: <20170908180133.GA20128@tassilo.jf.intel.com>
Commit-ID: 5e49f7321b06428ac68c51096cff9a4a55c3d4d6
Gitweb: http://git.kernel.org/tip/5e49f7321b06428ac68c51096cff9a4a55c3d4d6
Author: Andi Kleen <ak@linux.intel.com>
AuthorDate: Sun, 23 Jul 2017 21:55:39 -0700
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Wed, 13 Sep 2017 09:49:18 -0300
perf vendor events: Add JSON metrics for Haswell EP
Add JSON metrics for Haswell EP.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Link: http://lkml.kernel.org/r/20170908180133.GA20128@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
.../arch/x86/{haswell/hsw-metrics.json => haswellx/hsx-metrics.json} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/pmu-events/arch/x86/haswell/hsw-metrics.json b/tools/perf/pmu-events/arch/x86/haswellx/hsx-metrics.json
similarity index 98%
copy from tools/perf/pmu-events/arch/x86/haswell/hsw-metrics.json
copy to tools/perf/pmu-events/arch/x86/haswellx/hsx-metrics.json
index 03d8949..0bae5ed 100644
--- a/tools/perf/pmu-events/arch/x86/haswell/hsw-metrics.json
+++ b/tools/perf/pmu-events/arch/x86/haswellx/hsx-metrics.json
@@ -55,7 +55,7 @@
},
{
"BriefDescription": "Instruction-Level-Parallelism (average number of uops executed when there is at least 1 uop executed)",
- "MetricExpr": "( UOPS_EXECUTED.CORE / 2 / ( cpu@uops_executed.core\\,cmask\\=1@ / 2)) if #SMT_on else (UOPS_EXECUTED.CORE / cpu@uops_executed.core\\,cmask\\=1@)",
+ "MetricExpr": "( UOPS_EXECUTED.CORE / 2 / ( cpu@uops_executed.core\\,cmask\\=1@ / 2)) if #SMT_on else UOPS_EXECUTED.CORE / cpu@uops_executed.core\\,cmask\\=1@",
"MetricGroup": "Pipeline;Ports_Utilization",
"MetricName": "ILP"
},
next prev parent reply other threads:[~2017-09-22 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 18:01 [PULL] Please pull JSON Metrics for Intel CPUs Andi Kleen
2017-09-11 20:27 ` Arnaldo Carvalho de Melo
2017-09-22 16:38 ` [tip:perf/core] perf vendor events: Add JSON metrics for Sandy Bridge EP tip-bot for Andi Kleen
2017-09-22 16:39 ` [tip:perf/core] perf vendor events: Add JSON metrics for Ivy Bridge tip-bot for Andi Kleen
2017-09-22 16:39 ` [tip:perf/core] perf vendor events: Add JSON metrics for Haswell tip-bot for Andi Kleen
2017-09-22 16:40 ` [tip:perf/core] perf vendor events: Add JSON metrics for Ivy Town tip-bot for Andi Kleen
2017-09-22 16:40 ` tip-bot for Andi Kleen [this message]
2017-09-22 16:41 ` [tip:perf/core] perf vendor events: Add JSON metrics for Broadwell Server tip-bot for Andi Kleen
2017-09-22 16:41 ` [tip:perf/core] perf vendor events: Add JSON metrics for Broadwell DE tip-bot for Andi Kleen
2017-09-22 16:42 ` [tip:perf/core] perf vendor events: Add JSON metrics for Skylake server tip-bot for Andi Kleen
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=tip-5e49f7321b06428ac68c51096cff9a4a55c3d4d6@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome