mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tip-bot for Andi Kleen <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: acme@redhat.com, jolsa@redhat.com, tglx@linutronix.de,
	mingo@kernel.org, ak@linux.intel.com,
	linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: [tip:perf/core] perf vendor events: Add JSON metrics for Haswell
Date: Fri, 22 Sep 2017 09:39:55 -0700	[thread overview]
Message-ID: <tip-2099f51d1851c8955ed3406683be0b961c7792cb@git.kernel.org> (raw)
In-Reply-To: <20170908180133.GA20128@tassilo.jf.intel.com>

Commit-ID:  2099f51d1851c8955ed3406683be0b961c7792cb
Gitweb:     http://git.kernel.org/tip/2099f51d1851c8955ed3406683be0b961c7792cb
Author:     Andi Kleen <ak@linux.intel.com>
AuthorDate: Sun, 23 Jul 2017 21:51:47 -0700
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Wed, 13 Sep 2017 09:49:17 -0300

perf vendor events: Add JSON metrics for Haswell

Add JSON metrics for Haswell.

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>
---
 .../{ivybridge/ivb-metrics.json => haswell/hsw-metrics.json} | 12 +++---------
 1 file changed, 3 insertions(+), 9 deletions(-)

diff --git a/tools/perf/pmu-events/arch/x86/ivybridge/ivb-metrics.json b/tools/perf/pmu-events/arch/x86/haswell/hsw-metrics.json
similarity index 88%
copy from tools/perf/pmu-events/arch/x86/ivybridge/ivb-metrics.json
copy to tools/perf/pmu-events/arch/x86/haswell/hsw-metrics.json
index 057a832..03d8949 100644
--- a/tools/perf/pmu-events/arch/x86/ivybridge/ivb-metrics.json
+++ b/tools/perf/pmu-events/arch/x86/haswell/hsw-metrics.json
@@ -13,7 +13,7 @@
     },
     {
         "BriefDescription": "Rough Estimation of fraction of fetched lines bytes that were likely consumed by program instructions",
-        "MetricExpr": "min( 1 , UOPS_ISSUED.ANY / ( UOPS_RETIRED.RETIRE_SLOTS / INST_RETIRED.ANY * 32 * ( ICACHE.HIT + ICACHE.MISSES ) / 4) )",
+        "MetricExpr": "min( 1 , IDQ.MITE_UOPS / ( UOPS_RETIRED.RETIRE_SLOTS / INST_RETIRED.ANY * 16 * ( ICACHE.HIT + ICACHE.MISSES ) / 4.0 ) )",
         "MetricGroup": "Frontend",
         "MetricName": "IFetch_Line_Utilization"
     },
@@ -55,13 +55,13 @@
     },
     {
         "BriefDescription": "Instruction-Level-Parallelism (average number of uops executed when there is at least 1 uop executed)",
-        "MetricExpr": "UOPS_EXECUTED.THREAD / ( cpu@uops_executed.core\\,cmask\\=1@ / 2) if #SMT_on else UOPS_EXECUTED.CYCLES_GE_1_UOP_EXEC",
+	"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"
     },
     {
         "BriefDescription": "Average Branch Address Clear Cost (fraction of cycles)",
-        "MetricExpr": "2* ( RS_EVENTS.EMPTY_CYCLES - ICACHE.IFETCH_STALL ) / RS_EVENTS.EMPTY_END",
+        "MetricExpr": "2* ( RS_EVENTS.EMPTY_CYCLES - ICACHE.IFDATA_STALL  - ( 14 * ITLB_MISSES.STLB_HIT + ITLB_MISSES.WALK_DURATION ) ) / RS_EVENTS.EMPTY_END",
         "MetricGroup": "Unknown_Branches",
         "MetricName": "BAClear_Cost"
     },
@@ -96,12 +96,6 @@
         "MetricName": "CPU_Utilization"
     },
     {
-        "BriefDescription": "Giga Floating Point Operations Per Second",
-        "MetricExpr": "( 1*( FP_COMP_OPS_EXE.SSE_SCALAR_SINGLE + FP_COMP_OPS_EXE.SSE_SCALAR_DOUBLE ) + 2* FP_COMP_OPS_EXE.SSE_PACKED_DOUBLE + 4*( FP_COMP_OPS_EXE.SSE_PACKED_SINGLE + SIMD_FP_256.PACKED_DOUBLE ) + 8* SIMD_FP_256.PACKED_SINGLE ) / 1000000000 / duration_time",
-        "MetricGroup": "FLOPS;Summary",
-        "MetricName": "GFLOPs"
-    },
-    {
         "BriefDescription": "Average Frequency Utilization relative nominal frequency",
         "MetricExpr": "CPU_CLK_UNHALTED.THREAD / CPU_CLK_UNHALTED.REF_TSC",
         "MetricGroup": "Power",

  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-bot for Andi Kleen [this message]
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:perf/core] perf vendor events: Add JSON metrics for Haswell EP tip-bot for Andi Kleen
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-2099f51d1851c8955ed3406683be0b961c7792cb@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

all inboxes | Powered by JetHome®