From: Ian Rogers <irogers@google.com>
To: perry.taylor@intel.com, caleb.biggers@intel.com,
kshipra.bopardikar@intel.com,
Kan Liang <kan.liang@linux.intel.com>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
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@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Andi Kleen <ak@linux.intel.com>,
James Clark <james.clark@arm.com>,
John Garry <john.garry@huawei.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Sedat Dilek <sedat.dilek@gmail.com>
Cc: Stephane Eranian <eranian@google.com>, Ian Rogers <irogers@google.com>
Subject: [PATCH v3 30/30] perf vendor events: Update Intel snowridgex
Date: Wed, 27 Jul 2022 15:08:32 -0700 [thread overview]
Message-ID: <20220727220832.2865794-31-irogers@google.com> (raw)
In-Reply-To: <20220727220832.2865794-1-irogers@google.com>
Update to v1.20, the metrics are based on TMA 4.4 full.
Use script at:
https://github.com/intel/event-converter-for-linux-perf/blob/master/download_and_gen.py
to download and generate the latest events and metrics. Manually copy
the snowridgex files into perf and update mapfile.csv.
Tested on a non-snowridgex with 'perf test':
10: PMU events :
10.1: PMU event table sanity : Ok
10.2: PMU event map aliases : Ok
10.3: Parsing of PMU event table metrics : Ok
10.4: Parsing of PMU event table metrics with fake PMUs : Ok
This change just updates the version number.
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 c607f4155556..7f2d777fd97f 100644
--- a/tools/perf/pmu-events/arch/x86/mapfile.csv
+++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
@@ -24,11 +24,11 @@ GenuineIntel-6-8F,v1.04,sapphirerapids,core
GenuineIntel-6-(37|4C|4D),v14,silvermont,core
GenuineIntel-6-(4E|5E|8E|9E|A5|A6),v53,skylake,core
GenuineIntel-6-55-[01234],v1.28,skylakex,core
+GenuineIntel-6-86,v1.20,snowridgex,core
GenuineIntel-6-8[CD],v1.07,tigerlake,core
GenuineIntel-6-2C,v2,westmereep-dp,core
GenuineIntel-6-25,v3,westmereep-sp,core
GenuineIntel-6-2F,v3,westmereex,core
-GenuineIntel-6-86,v1,snowridgex,core
AuthenticAMD-23-([12][0-9A-F]|[0-9A-F]),v2,amdzen1,core
AuthenticAMD-23-[[:xdigit:]]+,v1,amdzen2,core
AuthenticAMD-25-[[:xdigit:]]+,v1,amdzen3,core
--
2.37.1.359.gd136c6c3e2-goog
next prev parent reply other threads:[~2022-07-27 22:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 22:08 [PATCH v3 00/30] Add generated latest Intel events and metrics Ian Rogers
2022-07-27 22:08 ` [PATCH v3 01/30] perf vendor events: Update Intel broadwellx Ian Rogers
2022-07-27 22:08 ` [PATCH v3 02/30] perf vendor events: Update Intel broadwell Ian Rogers
2022-07-27 22:08 ` [PATCH v3 03/30] perf vendor events: Update Intel broadwellde Ian Rogers
2022-07-27 22:08 ` [PATCH v3 04/30] perf vendor events: Update Intel alderlake Ian Rogers
2022-07-27 22:08 ` [PATCH v3 05/30] perf vendor events: Update bonnell mapfile.csv Ian Rogers
2022-07-27 22:08 ` [PATCH v3 06/30] perf vendor events: Update Intel cascadelakex Ian Rogers
2022-07-27 22:08 ` [PATCH v3 07/30] perf vendor events: Update Intel elkhartlake Ian Rogers
2022-07-27 22:08 ` [PATCH v3 08/30] perf vendor events: Update goldmont mapfile.csv Ian Rogers
2022-07-27 22:08 ` [PATCH v3 09/30] perf vendor events: Update goldmontplus mapfile.csv Ian Rogers
2022-07-27 22:08 ` [PATCH v3 10/30] perf vendor events: Update Intel haswell Ian Rogers
2022-07-27 22:08 ` [PATCH v3 11/30] perf vendor events: Update Intel haswellx Ian Rogers
2022-07-27 22:08 ` [PATCH v3 12/30] perf vendor events: Update Intel icelake Ian Rogers
2022-07-27 22:08 ` [PATCH v3 13/30] perf vendor events: Update Intel icelakex Ian Rogers
2022-07-27 22:08 ` [PATCH v3 14/30] perf vendor events: Update Intel ivybridge Ian Rogers
2022-07-27 22:08 ` [PATCH v3 15/30] perf vendor events: Update Intel ivytown Ian Rogers
2022-07-27 22:08 ` [PATCH v3 16/30] perf vendor events: Update Intel jaketown Ian Rogers
2022-07-27 22:08 ` [PATCH v3 17/30] perf vendor events: Update Intel knightslanding Ian Rogers
2022-07-27 22:08 ` [PATCH v3 18/30] perf vendor events: Add Intel meteorlake Ian Rogers
2022-07-27 22:08 ` [PATCH v3 19/30] perf vendor events: Update Intel nehalemep Ian Rogers
2022-07-27 22:08 ` [PATCH v3 20/30] perf vendor events: Update Intel nehalemex Ian Rogers
2022-07-27 22:08 ` [PATCH v3 21/30] perf vendor events: Update Intel sandybridge Ian Rogers
2022-07-29 8:41 ` Sedat Dilek
2022-07-29 8:47 ` Sedat Dilek
2022-07-29 14:35 ` Ian Rogers
2022-07-30 18:44 ` Sedat Dilek
2022-07-27 22:08 ` [PATCH v3 22/30] perf vendor events: Update Intel sapphirerapids Ian Rogers
2022-07-27 22:08 ` [PATCH v3 23/30] perf vendor events: Update Intel silvermont Ian Rogers
2022-07-27 22:08 ` [PATCH v3 24/30] perf vendor events: Update Intel skylake Ian Rogers
2022-07-27 22:08 ` [PATCH v3 25/30] perf vendor events: Update Intel skylakex Ian Rogers
2022-07-27 22:08 ` [PATCH v3 26/30] perf vendor events: Update Intel tigerlake Ian Rogers
2022-07-27 22:08 ` [PATCH v3 27/30] perf vendor events: Update Intel westmereep-dp Ian Rogers
2022-07-27 22:08 ` [PATCH v3 28/30] perf vendor events: Update Intel westmereep-sp Ian Rogers
2022-07-27 22:08 ` [PATCH v3 29/30] perf vendor events: Update Intel westmereex Ian Rogers
2022-07-27 22:08 ` Ian Rogers [this message]
2022-07-28 19:14 ` [PATCH v3 00/30] Add generated latest Intel events and metrics Arnaldo Carvalho de Melo
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=20220727220832.2865794-31-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=caleb.biggers@intel.com \
--cc=eranian@google.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kshipra.bopardikar@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=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=sedat.dilek@gmail.com \
--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
all inboxes | Powered by JetHome®