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>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] Updates to sapphirerapids, alderlake and icelakex events
Date: Tue, 11 Apr 2023 16:44:37 -0700 [thread overview]
Message-ID: <20230411234440.3313680-1-irogers@google.com> (raw)
Changes largely stemming from:
https://github.com/intel/perfmon/pull/68
Changes generated by:
https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
Ian Rogers (3):
perf vendor events: Update alderlake to v1.20
perf vendor events: Update icelakex to v1.20
perf vendor events: Update sapphirerapids to v1.12
.../pmu-events/arch/x86/alderlake/other.json | 3 +-
.../arch/x86/alderlake/pipeline.json | 4 +-
.../arch/x86/icelakex/uncore-other.json | 2 +-
tools/perf/pmu-events/arch/x86/mapfile.csv | 8 +-
.../arch/x86/sapphirerapids/other.json | 3 +-
.../arch/x86/sapphirerapids/pipeline.json | 4 +-
.../x86/sapphirerapids/uncore-memory.json | 794 +-
.../arch/x86/sapphirerapids/uncore-other.json | 18656 +++++++++++++---
.../arch/x86/sapphirerapids/uncore-power.json | 107 +
9 files changed, 16977 insertions(+), 2604 deletions(-)
--
2.40.0.577.gac1e443424-goog
next reply other threads:[~2023-04-11 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 23:44 Ian Rogers [this message]
2023-04-11 23:44 ` [PATCH v1 1/3] perf vendor events: Update alderlake to v1.20 Ian Rogers
2023-04-11 23:44 ` [PATCH v1 2/3] perf vendor events: Update icelakex " Ian Rogers
2023-04-11 23:44 ` [PATCH v1 3/3] perf vendor events: Update sapphirerapids to v1.12 Ian Rogers
2023-04-12 13:30 ` [PATCH v1 0/3] Updates to sapphirerapids, alderlake and icelakex events 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=20230411234440.3313680-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.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=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