From: Ian Rogers <irogers@google.com>
To: Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
perry.taylor@intel.com, caleb.biggers@intel.com,
kshipra.bopardikar@intel.com, samantha.alt@intel.com,
ahmad.yasin@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@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
John Garry <john.garry@huawei.com>,
James Clark <james.clark@arm.com>,
Kajol Jain <kjain@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Miaoqian Lin <linmq006@gmail.com>,
Florian Fischer <florian.fischer@muhq.space>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Stephane Eranian <eranian@google.com>, Ian Rogers <irogers@google.com>
Subject: [PATCH v2 09/22] perf vendor events: Update elkhartlake cpuids
Date: Fri, 30 Sep 2022 23:06:23 -0700 [thread overview]
Message-ID: <20221001060636.2661983-10-irogers@google.com> (raw)
In-Reply-To: <20221001060636.2661983-1-irogers@google.com>
Add cpuid that was added to https://download.01.org/perfmon/mapfile.csv
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 bc873a1e84e1..6c8188404db8 100644
--- a/tools/perf/pmu-events/arch/x86/mapfile.csv
+++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
@@ -5,7 +5,7 @@ GenuineIntel-6-(3D|47),v26,broadwell,core
GenuineIntel-6-56,v23,broadwellde,core
GenuineIntel-6-4F,v19,broadwellx,core
GenuineIntel-6-55-[56789ABCDEF],v1.16,cascadelakex,core
-GenuineIntel-6-96,v1.03,elkhartlake,core
+GenuineIntel-6-9[6C],v1.03,elkhartlake,core
GenuineIntel-6-5[CF],v13,goldmont,core
GenuineIntel-6-7A,v1.01,goldmontplus,core
GenuineIntel-6-(3C|45|46),v31,haswell,core
--
2.38.0.rc1.362.ged0d419d3c-goog
next prev parent reply other threads:[~2022-10-01 6:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 6:06 [PATCH v2 00/22] Improvements to Intel perf metrics Ian Rogers
2022-10-01 6:06 ` [PATCH v2 01/22] perf expr: Allow a double if expression Ian Rogers
2022-10-01 6:06 ` [PATCH v2 02/22] perf expr: Remove jevents case workaround Ian Rogers
2022-10-01 6:06 ` [PATCH v2 03/22] perf metrics: Don't scale counts going into metrics Ian Rogers
2022-10-01 6:06 ` [PATCH v2 06/22] perf vendor events: Update Intel broadwell Ian Rogers
2022-10-01 6:06 ` Ian Rogers [this message]
2022-10-01 6:06 ` [PATCH v2 10/22] perf vendor events: Update Intel haswell Ian Rogers
2022-10-01 6:06 ` [PATCH v2 12/22] perf vendor events: Update Intel icelake Ian Rogers
2022-10-01 6:06 ` [PATCH v2 14/22] perf vendor events: Update Intel ivybridge Ian Rogers
2022-10-01 6:06 ` [PATCH v2 16/22] perf vendor events: Update Intel jaketown Ian Rogers
2022-10-01 6:06 ` [PATCH v2 17/22] perf vendor events: Update Intel sandybridge Ian Rogers
2022-10-01 6:06 ` [PATCH v2 19/22] perf vendor events: Update silvermont cpuids Ian Rogers
2022-10-01 6:06 ` [PATCH v2 21/22] perf vendor events: Update Intel tigerlake Ian Rogers
2022-10-01 6:06 ` [PATCH v2 22/22] perf vendor events: Update Intel broadwellde 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=20221001060636.2661983-10-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=ahmad.yasin@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=eranian@google.com \
--cc=florian.fischer@muhq.space \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=kshipra.bopardikar@intel.com \
--cc=linmq006@gmail.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=tmricht@linux.ibm.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).