From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Kan Liang <kan.liang@linux.intel.com>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Edward Baker <edward.baker@intel.com>
Subject: [PATCH v1 8/9] perf vendor events intel: Update bonnell version number to v5
Date: Wed, 25 Oct 2023 17:31:48 -0700 [thread overview]
Message-ID: <20231026003149.3287633-8-irogers@google.com> (raw)
In-Reply-To: <20231026003149.3287633-1-irogers@google.com>
Spelling fixes were already incorporated in the Linux perf tree,
update the version number to reflect this.
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/pmu-events/arch/x86/mapfile.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/pmu-events/arch/x86/mapfile.csv b/tools/perf/pmu-events/arch/x86/mapfile.csv
index 0dee3de3187c..e571683f59f3 100644
--- a/tools/perf/pmu-events/arch/x86/mapfile.csv
+++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
@@ -1,7 +1,7 @@
Family-model,Version,Filename,EventType
GenuineIntel-6-(97|9A|B7|BA|BF),v1.23,alderlake,core
GenuineIntel-6-BE,v1.23,alderlaken,core
-GenuineIntel-6-(1C|26|27|35|36),v4,bonnell,core
+GenuineIntel-6-(1C|26|27|35|36),v5,bonnell,core
GenuineIntel-6-(3D|47),v28,broadwell,core
GenuineIntel-6-56,v11,broadwellde,core
GenuineIntel-6-4F,v22,broadwellx,core
--
2.42.0.758.gaed0368e0e-goog
next prev parent reply other threads:[~2023-10-26 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 0:31 [PATCH v1 1/9] perf vendor events intel: Update alderlake/alderlake events to v1.23 Ian Rogers
2023-10-26 0:31 ` [PATCH v1 2/9] perf vendor events intel: Update emeraldrapids to v1.01 Ian Rogers
2023-10-26 0:31 ` [PATCH v1 3/9] perf vendor events intel: Update a spelling in haswell/haswellx Ian Rogers
2023-10-26 0:31 ` [PATCH v1 4/9] perf vendor events intel: Add typo fix for ivybridge FP Ian Rogers
2023-10-26 0:31 ` [PATCH v1 5/9] perf vendor events intel: Update knightslanding events to v16 Ian Rogers
2023-10-26 0:31 ` [PATCH v1 6/9] perf vendor events intel: Update meteorlake events to v1.06 Ian Rogers
2023-10-26 0:31 ` [PATCH v1 7/9] perf vendor events intel: Update westmereex events to v4 Ian Rogers
2023-10-26 0:31 ` Ian Rogers [this message]
2023-10-26 0:31 ` [PATCH v1 9/9] perf vendor events intel: Update tsx_cycles_per_elision metrics Ian Rogers
2023-10-26 18:16 ` [PATCH v1 1/9] perf vendor events intel: Update alderlake/alderlake events to v1.23 Liang, Kan
2023-10-30 19:00 ` 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=20231026003149.3287633-8-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=edward.baker@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=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=zhengjun.xing@linux.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).