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>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Perry Taylor <perry.taylor@intel.com>,
Samantha Alt <samantha.alt@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>,
Weilin Wang <weilin.wang@intel.com>,
Edward Baker <edward.baker@intel.com>
Cc: Stephane Eranian <eranian@google.com>
Subject: [PATCH v1 03/30] perf vendor events intel: Update broadwell events to v29
Date: Tue, 13 Feb 2024 17:17:52 -0800 [thread overview]
Message-ID: <20240214011820.644458-4-irogers@google.com> (raw)
In-Reply-To: <20240214011820.644458-1-irogers@google.com>
Update broadwell events to v29 released in:
https://github.com/intel/perfmon/commit/47117146c6b9e38811618beca31eba4e41c3d874
Updates "must be precise" on RTM_RETIRED.ABORTED.
Event json automatically generated by:
https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/pmu-events/arch/x86/broadwell/memory.json | 2 +-
tools/perf/pmu-events/arch/x86/mapfile.csv | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/pmu-events/arch/x86/broadwell/memory.json b/tools/perf/pmu-events/arch/x86/broadwell/memory.json
index ac7cdb831960..b01ed47072bc 100644
--- a/tools/perf/pmu-events/arch/x86/broadwell/memory.json
+++ b/tools/perf/pmu-events/arch/x86/broadwell/memory.json
@@ -2005,7 +2005,7 @@
"BriefDescription": "Number of times RTM abort was triggered",
"EventCode": "0xc9",
"EventName": "RTM_RETIRED.ABORTED",
- "PEBS": "1",
+ "PEBS": "2",
"PublicDescription": "Number of times RTM abort was triggered .",
"SampleAfterValue": "2000003",
"UMask": "0x4"
diff --git a/tools/perf/pmu-events/arch/x86/mapfile.csv b/tools/perf/pmu-events/arch/x86/mapfile.csv
index 5bda5d498841..7b30c0eb036a 100644
--- a/tools/perf/pmu-events/arch/x86/mapfile.csv
+++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
@@ -2,7 +2,7 @@ Family-model,Version,Filename,EventType
GenuineIntel-6-(97|9A|B7|BA|BF),v1.24,alderlake,core
GenuineIntel-6-BE,v1.24,alderlaken,core
GenuineIntel-6-(1C|26|27|35|36),v5,bonnell,core
-GenuineIntel-6-(3D|47),v28,broadwell,core
+GenuineIntel-6-(3D|47),v29,broadwell,core
GenuineIntel-6-56,v11,broadwellde,core
GenuineIntel-6-4F,v22,broadwellx,core
GenuineIntel-6-55-[56789ABCDEF],v1.20,cascadelakex,core
--
2.43.0.687.g38aa6559b0-goog
next prev parent reply other threads:[~2024-02-14 1:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 1:17 [PATCH v1 00/30] perf vendor event and TMA 4.7 metric update Ian Rogers
2024-02-14 1:17 ` [PATCH v1 01/30] perf vendor events intel: Update alderlake events to v1.24 Ian Rogers
2024-02-14 1:17 ` [PATCH v1 02/30] perf vendor events intel: Update alderlaken " Ian Rogers
2024-02-14 1:17 ` Ian Rogers [this message]
2024-02-14 1:17 ` [PATCH v1 04/30] perf vendor events intel: Update emeraldrapids events to v1.03 Ian Rogers
2024-02-14 1:17 ` [PATCH v1 05/30] perf vendor events intel: Update grandridge events to v1.01 Ian Rogers
2024-02-14 1:17 ` [PATCH v1 06/30] perf vendor events intel: Update haswell events to v35 Ian Rogers
2024-02-14 1:17 ` [PATCH v1 07/30] perf vendor events intel: Update icelake events to v1.21 Ian Rogers
2024-02-14 1:17 ` [PATCH v1 08/30] perf vendor events intel: Update meteorlake events to v1.07 Ian Rogers
2024-02-14 1:17 ` [PATCH v1 09/30] perf vendor events intel: Update rocketlake events to v1.02 Ian Rogers
2024-02-14 1:17 ` [PATCH v1 10/30] perf vendor events intel: Update sierraforst events to v1.01 Ian Rogers
2024-02-14 1:18 ` [PATCH v1 11/30] perf vendor events intel: Update skylake events to v58 Ian Rogers
2024-02-14 1:18 ` [PATCH v1 12/30] perf vendor events intel: Update tigerlake events to v1.15 Ian Rogers
2024-02-14 1:18 ` [PATCH v1 13/30] perf vendor events intel: Update alderlake TMA metrics to 4.7 Ian Rogers
2024-02-14 1:18 ` [PATCH v1 14/30] perf vendor events intel: Update broadwell " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 15/30] perf vendor events intel: Update broadwellde " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 16/30] perf vendor events intel: Update broadwellx " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 17/30] perf vendor events intel: Update cascadelakex " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 18/30] perf vendor events intel: Update haswell " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 19/30] perf vendor events intel: Update haswellx " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 20/30] perf vendor events intel: Update icelake " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 21/30] perf vendor events intel: Update icelakex " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 22/30] perf vendor events intel: Update ivybridge " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 23/30] perf vendor events intel: Update ivytown " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 24/30] perf vendor events intel: Update jaketown " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 25/30] perf vendor events intel: Update rocketlake " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 26/30] perf vendor events intel: Update sandybridge " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 27/30] perf vendor events intel: Update sapphirerapids " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 28/30] perf vendor events intel: Update skylake " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 29/30] perf vendor events intel: Update skylakex " Ian Rogers
2024-02-14 1:18 ` [PATCH v1 30/30] perf vendor events intel: Update tigerlake " Ian Rogers
2024-02-14 15:44 ` [PATCH v1 00/30] perf vendor event and TMA 4.7 metric update Liang, Kan
2024-02-21 1:59 ` Namhyung Kim
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=20240214011820.644458-4-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=eranian@google.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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@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;
as well as URLs for NNTP newsgroup(s).