From: Ian Rogers <irogers@google.com>
To: "Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Ian Rogers" <irogers@google.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Caleb Biggers" <caleb.biggers@intel.com>,
"Weilin Wang" <weilin.wang@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Perry Taylor" <perry.taylor@intel.com>,
"Thomas Falcon" <thomas.falcon@intel.com>
Subject: [PATCH v3 04/35] perf vendor events: Update bonnell events
Date: Tue, 25 Mar 2025 12:03:20 -0700 [thread overview]
Message-ID: <20250325190352.59241-5-irogers@google.com> (raw)
In-Reply-To: <20250325190352.59241-1-irogers@google.com>
Move DISPATCH_BLOCKED.ANY to the pipeline topic.
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/pmu-events/arch/x86/bonnell/other.json | 8 --------
tools/perf/pmu-events/arch/x86/bonnell/pipeline.json | 8 ++++++++
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/tools/perf/pmu-events/arch/x86/bonnell/other.json b/tools/perf/pmu-events/arch/x86/bonnell/other.json
index 3a55c101fbf7..6e6f64b96834 100644
--- a/tools/perf/pmu-events/arch/x86/bonnell/other.json
+++ b/tools/perf/pmu-events/arch/x86/bonnell/other.json
@@ -323,14 +323,6 @@
"SampleAfterValue": "2000000",
"UMask": "0x2"
},
- {
- "BriefDescription": "Memory cluster signals to block micro-op dispatch for any reason",
- "Counter": "0,1",
- "EventCode": "0x9",
- "EventName": "DISPATCH_BLOCKED.ANY",
- "SampleAfterValue": "200000",
- "UMask": "0x20"
- },
{
"BriefDescription": "Number of Enhanced Intel SpeedStep(R) Technology (EIST) transitions",
"Counter": "0,1",
diff --git a/tools/perf/pmu-events/arch/x86/bonnell/pipeline.json b/tools/perf/pmu-events/arch/x86/bonnell/pipeline.json
index 9ff032ab11e2..48d3d053a369 100644
--- a/tools/perf/pmu-events/arch/x86/bonnell/pipeline.json
+++ b/tools/perf/pmu-events/arch/x86/bonnell/pipeline.json
@@ -211,6 +211,14 @@
"SampleAfterValue": "2000000",
"UMask": "0x1"
},
+ {
+ "BriefDescription": "Memory cluster signals to block micro-op dispatch for any reason",
+ "Counter": "0,1",
+ "EventCode": "0x9",
+ "EventName": "DISPATCH_BLOCKED.ANY",
+ "SampleAfterValue": "200000",
+ "UMask": "0x20"
+ },
{
"BriefDescription": "Divide operations retired",
"Counter": "0,1",
--
2.49.0.395.g12beb8f557-goog
next prev parent reply other threads:[~2025-03-25 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 19:03 [PATCH v3 00/35] GNR retirement latencies, topic and metric updates Ian Rogers
2025-03-25 19:03 ` [PATCH v3 01/35] perf vendor events: Update alderlake events/metrics Ian Rogers
2025-03-25 19:03 ` [PATCH v3 02/35] perf vendor events: Update AlderlakeN events/metrics Ian Rogers
2025-03-25 19:03 ` [PATCH v3 03/35] perf vendor events: Update arrowlake events/metrics Ian Rogers
2025-03-25 19:03 ` Ian Rogers [this message]
2025-03-25 19:03 ` [PATCH v3 05/35] perf vendor events: Update broadwell metrics Ian Rogers
2025-03-25 19:03 ` [PATCH v3 06/35] perf vendor events: Update broadwellde metrics Ian Rogers
2025-03-25 19:03 ` [PATCH v3 07/35] perf vendor events: Update broadwellx metrics Ian Rogers
2025-03-25 19:03 ` [PATCH v3 08/35] perf vendor events: Update cascadelakex events/metrics Ian Rogers
-- strict thread matches above, loose matches on Subject: below --
2025-03-26 0:03 [PATCH v3 00/35] GNR retirement latencies, topic and metric updates Ian Rogers
2025-03-26 0:04 ` [PATCH v3 04/35] perf vendor events: Update bonnell events Ian Rogers
2025-03-25 17:52 [PATCH v3 00/35] GNR retirement latencies, topic and metric updates Ian Rogers
2025-03-25 17:52 ` [PATCH v3 04/35] perf vendor events: Update bonnell events Ian Rogers
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=20250325190352.59241-5-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=caleb.biggers@intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
--cc=weilin.wang@intel.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