From: kan.liang@linux.intel.com
To: peterz@infradead.org, acme@kernel.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, jolsa@kernel.org, eranian@google.com,
alexander.shishkin@linux.intel.com, ak@linux.intel.com,
Kan Liang <kan.liang@linux.intel.com>
Subject: [PATCH V5 08/14] perf/x86/intel: Export TopDown events for Icelake
Date: Sun, 3 Nov 2019 15:29:14 -0800 [thread overview]
Message-ID: <20191103232920.20309-9-kan.liang@linux.intel.com> (raw)
In-Reply-To: <20191103232920.20309-1-kan.liang@linux.intel.com>
From: Kan Liang <kan.liang@linux.intel.com>
Export new TopDown metrics events for perf that map to the sub metrics
in the metrics register, and another for the new slots fixed counter.
This makes the new fixed counters in Icelake visible to the perf
user tools.
Originally-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
---
No changes since V4
arch/x86/events/intel/core.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
index 0d1a327c18fc..d913dda3e1c2 100644
--- a/arch/x86/events/intel/core.c
+++ b/arch/x86/events/intel/core.c
@@ -321,6 +321,12 @@ EVENT_ATTR_STR_HT(topdown-recovery-bubbles, td_recovery_bubbles,
EVENT_ATTR_STR_HT(topdown-recovery-bubbles.scale, td_recovery_bubbles_scale,
"4", "2");
+EVENT_ATTR_STR(slots, slots, "event=0x00,umask=0x4");
+EVENT_ATTR_STR(topdown-retiring, td_retiring, "event=0x00,umask=0x10");
+EVENT_ATTR_STR(topdown-bad-spec, td_bad_spec, "event=0x00,umask=0x11");
+EVENT_ATTR_STR(topdown-fe-bound, td_fe_bound, "event=0x00,umask=0x12");
+EVENT_ATTR_STR(topdown-be-bound, td_be_bound, "event=0x00,umask=0x13");
+
static struct attribute *snb_events_attrs[] = {
EVENT_PTR(td_slots_issued),
EVENT_PTR(td_slots_retired),
@@ -4567,6 +4573,15 @@ static struct attribute *icl_events_attrs[] = {
NULL,
};
+static struct attribute *icl_td_events_attrs[] = {
+ EVENT_PTR(slots),
+ EVENT_PTR(td_retiring),
+ EVENT_PTR(td_bad_spec),
+ EVENT_PTR(td_fe_bound),
+ EVENT_PTR(td_be_bound),
+ NULL,
+};
+
static struct attribute *icl_tsx_events_attrs[] = {
EVENT_PTR(tx_start),
EVENT_PTR(tx_abort),
@@ -5342,6 +5357,7 @@ __init int intel_pmu_init(void)
hsw_format_attr : nhm_format_attr;
extra_skl_attr = skl_format_attr;
mem_attr = icl_events_attrs;
+ td_attr = icl_td_events_attrs;
tsx_attr = icl_tsx_events_attrs;
x86_pmu.rtm_abort_event = X86_CONFIG(.event=0xca, .umask=0x02);
x86_pmu.lbr_pt_coexist = true;
--
2.17.1
next prev parent reply other threads:[~2019-11-03 23:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 23:29 [PATCH V5 00/14] TopDown metrics support for Icelake kan.liang
2019-11-03 23:29 ` [PATCH V5 01/14] perf/x86/intel: Introduce the fourth fixed counter kan.liang
2019-11-03 23:29 ` [PATCH V5 02/14] perf/x86/intel: Set correct mask for TOPDOWN.SLOTS kan.liang
2019-11-03 23:29 ` [PATCH V5 03/14] perf/x86/intel: Move BTS index to 47 kan.liang
2019-11-03 23:29 ` [PATCH V5 04/14] perf/x86/intel: Basic support for metrics counters kan.liang
2019-11-03 23:29 ` [PATCH V5 05/14] perf/x86/intel: Fix the name of perf capabilities for perf METRICS kan.liang
2019-11-03 23:29 ` [PATCH V5 06/14] perf/x86/intel: Support hardware TopDown metrics kan.liang
2019-11-03 23:29 ` [PATCH V5 07/14] perf/x86/intel: Support per thread RDPMC " kan.liang
2019-11-03 23:29 ` kan.liang [this message]
2019-11-03 23:29 ` [PATCH V5 09/14] perf/x86/intel: Disable sampling read slots and topdown kan.liang
2019-11-03 23:29 ` [PATCH V5 10/14] perf/x86/intel: Name global status bit in NMI handler kan.liang
2019-11-03 23:29 ` [PATCH V5 11/14] perf/x86: Use event_base_rdpmc for RDPMC userspace support kan.liang
2019-11-03 23:29 ` [PATCH V5 12/14] perf, tools, stat: Support new per thread TopDown metrics kan.liang
2019-11-03 23:29 ` [PATCH V5 13/14] perf, tools, stat: Check Topdown Metric group kan.liang
2019-11-03 23:29 ` [PATCH V5 14/14] perf, tools: Add documentation for topdown metrics kan.liang
2019-11-11 12:23 ` [PATCH V5 00/14] TopDown metrics support for Icelake Liang, Kan
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=20191103232920.20309-9-kan.liang@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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