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 v2 30/32] perf vendor events: Update Intel westmereex
Date: Mon, 25 Jul 2022 15:36:31 -0700 [thread overview]
Message-ID: <20220725223633.2301737-31-irogers@google.com> (raw)
In-Reply-To: <20220725223633.2301737-1-irogers@google.com>
Update to v3, 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 westmereex files into perf and update mapfile.csv. This
change just aligns whitespace and updates the version number.
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/pmu-events/arch/x86/mapfile.csv | 2 +-
tools/perf/pmu-events/arch/x86/westmereex/floating-point.json | 2 +-
tools/perf/pmu-events/arch/x86/westmereex/frontend.json | 2 +-
tools/perf/pmu-events/arch/x86/westmereex/virtual-memory.json | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/perf/pmu-events/arch/x86/mapfile.csv b/tools/perf/pmu-events/arch/x86/mapfile.csv
index 4c00b050ebc6..4cf708477680 100644
--- a/tools/perf/pmu-events/arch/x86/mapfile.csv
+++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
@@ -27,7 +27,7 @@ GenuineIntel-6-55-[01234],v1.28,skylakex,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,v2,westmereex,core
+GenuineIntel-6-2F,v3,westmereex,core
GenuineIntel-6-86,v1,tremontx,core
AuthenticAMD-23-([12][0-9A-F]|[0-9A-F]),v2,amdzen1,core
AuthenticAMD-23-[[:xdigit:]]+,v1,amdzen2,core
diff --git a/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json b/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
index 39af1329224a..666e466d351c 100644
--- a/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
+++ b/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
@@ -226,4 +226,4 @@
"SampleAfterValue": "200000",
"UMask": "0x8"
}
-]
\ No newline at end of file
+]
diff --git a/tools/perf/pmu-events/arch/x86/westmereex/frontend.json b/tools/perf/pmu-events/arch/x86/westmereex/frontend.json
index 8ac5c24888c5..c561ac24d91d 100644
--- a/tools/perf/pmu-events/arch/x86/westmereex/frontend.json
+++ b/tools/perf/pmu-events/arch/x86/westmereex/frontend.json
@@ -23,4 +23,4 @@
"SampleAfterValue": "2000000",
"UMask": "0x1"
}
-]
\ No newline at end of file
+]
diff --git a/tools/perf/pmu-events/arch/x86/westmereex/virtual-memory.json b/tools/perf/pmu-events/arch/x86/westmereex/virtual-memory.json
index 5d1e017d1261..0c3501e6e5a3 100644
--- a/tools/perf/pmu-events/arch/x86/westmereex/virtual-memory.json
+++ b/tools/perf/pmu-events/arch/x86/westmereex/virtual-memory.json
@@ -170,4 +170,4 @@
"SampleAfterValue": "200000",
"UMask": "0x1"
}
-]
\ No newline at end of file
+]
--
2.37.1.359.gd136c6c3e2-goog
next prev parent reply other threads:[~2022-07-25 22:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 22:36 [PATCH v2 00/32] Add generated latest Intel events and metrics Ian Rogers
2022-07-25 22:36 ` [PATCH v2 01/32] perf test: Avoid sysfs state affecting fake events Ian Rogers
2022-07-25 22:36 ` [PATCH v2 06/32] perf vendor events: Update bonnell mapfile.csv Ian Rogers
2022-07-25 22:36 ` [PATCH v2 09/32] perf vendor events: Update goldmont mapfile.csv Ian Rogers
2022-07-25 22:36 ` [PATCH v2 10/32] perf vendor events: Update goldmontplus mapfile.csv Ian Rogers
2022-07-25 22:36 ` [PATCH v2 11/32] perf vendor events: Update Intel haswell Ian Rogers
2022-07-25 22:36 ` [PATCH v2 13/32] perf vendor events: Update Intel icelake Ian Rogers
2022-07-25 22:36 ` [PATCH v2 14/32] perf vendor events: Update Intel icelakex Ian Rogers
2022-07-25 22:36 ` [PATCH v2 15/32] perf vendor events: Update Intel ivybridge Ian Rogers
2022-07-25 22:36 ` [PATCH v2 19/32] perf vendor events: Add Intel meteorlake Ian Rogers
2022-07-25 22:36 ` [PATCH v2 20/32] perf vendor events: Update Intel nehalemep Ian Rogers
2022-07-25 22:36 ` [PATCH v2 22/32] perf vendor events: Update Intel sandybridge Ian Rogers
2022-07-25 22:36 ` [PATCH v2 24/32] perf vendor events: Update Intel silvermont Ian Rogers
2022-07-25 22:36 ` [PATCH v2 25/32] perf vendor events: Update Intel skylake Ian Rogers
2022-07-25 22:36 ` [PATCH v2 27/32] perf vendor events: Update Intel tigerlake Ian Rogers
2022-07-25 22:36 ` [PATCH v2 28/32] perf vendor events: Update Intel westmereep-dp Ian Rogers
2022-07-25 22:36 ` [PATCH v2 29/32] perf vendor events: Update Intel westmereep-sp Ian Rogers
2022-07-25 22:36 ` Ian Rogers [this message]
2022-07-25 22:36 ` [PATCH v2 31/32] perf vendor events intel: Rename tremontx to snowridgex 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=20220725223633.2301737-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;
as well as URLs for NNTP newsgroup(s).