From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Cc: Weilin Wang <weilin.wang@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>
Subject: Re: [PATCH v1 13/37] perf vendor events: Update grandridge events and add counter information
Date: Tue, 18 Jun 2024 09:45:14 -0400 [thread overview]
Message-ID: <00ac4787-c290-424f-8461-7ba300a4c1a9@linux.intel.com> (raw)
In-Reply-To: <20240614230146.3783221-14-irogers@google.com>
On 2024-06-14 7:01 p.m., Ian Rogers wrote:
> Update events from v1.01 to v1.02.
The subject has a typo. It should be "perf vendor events: Update
graniterapids events and add counter information", not grandridge.
Thanks,
Kan
>
> Bring in the event updates v1.02:
> https://github.com/intel/perfmon/commit/0ff9f681bd07d0e84026c52f4941d21b1cd4c171
>
> Add counter information. The most recent RFC patch set using this
> information:
> https://lore.kernel.org/lkml/20240412210756.309828-1-weilin.wang@intel.com/
>
> There are over 1000 new events.
>
> Co-authored-by: Weilin Wang <weilin.wang@intel.com>
> Co-authored-by: Caleb Biggers <caleb.biggers@intel.com>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> .../arch/x86/graniterapids/cache.json | 825 ++++
> .../arch/x86/graniterapids/counter.json | 77 +
> .../x86/graniterapids/floating-point.json | 242 ++
> .../arch/x86/graniterapids/frontend.json | 469 ++-
> .../arch/x86/graniterapids/memory.json | 175 +-
> .../arch/x86/graniterapids/other.json | 150 +-
> .../arch/x86/graniterapids/pipeline.json | 1009 ++++-
> .../arch/x86/graniterapids/uncore-cache.json | 3674 +++++++++++++++++
> .../arch/x86/graniterapids/uncore-cxl.json | 31 +
> .../graniterapids/uncore-interconnect.json | 1849 +++++++++
> .../arch/x86/graniterapids/uncore-io.json | 1901 +++++++++
> .../arch/x86/graniterapids/uncore-memory.json | 449 ++
> .../arch/x86/graniterapids/uncore-power.json | 11 +
> .../x86/graniterapids/virtual-memory.json | 159 +
> tools/perf/pmu-events/arch/x86/mapfile.csv | 2 +-
> 15 files changed, 10975 insertions(+), 48 deletions(-)
> create mode 100644 tools/perf/pmu-events/arch/x86/graniterapids/counter.json
> create mode 100644 tools/perf/pmu-events/arch/x86/graniterapids/floating-point.json
> create mode 100644 tools/perf/pmu-events/arch/x86/graniterapids/uncore-cache.json
> create mode 100644 tools/perf/pmu-events/arch/x86/graniterapids/uncore-cxl.json
> create mode 100644 tools/perf/pmu-events/arch/x86/graniterapids/uncore-interconnect.json
> create mode 100644 tools/perf/pmu-events/arch/x86/graniterapids/uncore-io.json
> create mode 100644 tools/perf/pmu-events/arch/x86/graniterapids/uncore-memory.json
> create mode 100644 tools/perf/pmu-events/arch/x86/graniterapids/uncore-power.json
next prev parent reply other threads:[~2024-06-18 13:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 23:01 [PATCH v1 00/37] Update Intel perf vendor events Ian Rogers
2024-06-14 23:01 ` [PATCH v1 01/37] perf vendor events: Update alderlake events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 02/37] perf vendor events: Update alderlaken events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 03/37] perf vendor events: Add bonnell counter information Ian Rogers
2024-06-14 23:01 ` [PATCH v1 04/37] perf vendor events: Update broadwell metrics add event " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 05/37] perf vendor events: Update broadwellde " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 06/37] perf vendor events: Update broadwellx " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 07/37] perf vendor events: Update cascadelakex events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 08/37] perf vendor events: Update elkhartlake events Ian Rogers
2024-06-14 23:01 ` [PATCH v1 09/37] perf vendor events: Add/update emeraldrapids events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 10/37] perf vendor events: Add goldmont counter information Ian Rogers
2024-06-14 23:01 ` [PATCH v1 11/37] perf vendor events: Add goldmontplus " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 12/37] perf vendor events: Update/add grandridge events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 13/37] perf vendor events: Update grandridge events and add counter information Ian Rogers
2024-06-18 13:45 ` Liang, Kan [this message]
2024-06-20 18:07 ` Ian Rogers
2024-06-14 23:01 ` [PATCH v1 14/37] perf vendor events: Add haswell " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 15/37] perf vendor events: Update haswellx metrics add event " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 16/37] perf vendor events: Add/update icelake events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 17/37] perf vendor events: Add/update icelakex events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 18/37] perf vendor events: Update ivybridge metrics add event counter information Ian Rogers
2024-06-14 23:01 ` [PATCH v1 19/37] perf vendor events: Update ivytown " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 20/37] perf vendor events: Update jaketown " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 21/37] perf vendor events: Add knightslanding " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 22/37] perf vendor events: Add lunarlake " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 23/37] perf vendor events: Update meteorlake events and add " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 24/37] perf vendor events: Add nehalemep " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 25/37] perf vendor events: Add nehalemex " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 26/37] perf vendor events: Add/update rocketlake events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 27/37] perf vendor events: Update sandybridge metrics add event counter information Ian Rogers
2024-06-14 23:01 ` [PATCH v1 28/37] perf vendor events: Add/update sapphirerapids events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 29/37] perf vendor events: Add/update sierraforest events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 30/37] perf vendor events: Add silvermont counter information Ian Rogers
2024-06-14 23:01 ` [PATCH v1 31/37] perf vendor events: Add/update skylake events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 32/37] perf vendor events: Add/update skylakex events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 33/37] perf vendor events: Add snowridgex counter information Ian Rogers
2024-06-14 23:01 ` [PATCH v1 34/37] perf vendor events: Add/update tigerlake events/metrics Ian Rogers
2024-06-14 23:01 ` [PATCH v1 35/37] perf vendor events: Add westmereep-dp counter information Ian Rogers
2024-06-14 23:01 ` [PATCH v1 36/37] perf vendor events: Add westmereep-sp " Ian Rogers
2024-06-14 23:01 ` [PATCH v1 37/37] perf vendor events: Add westmereex " Ian Rogers
2024-06-18 13:50 ` [PATCH v1 00/37] Update Intel perf vendor events Liang, Kan
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=00ac4787-c290-424f-8461-7ba300a4c1a9@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=caleb.biggers@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--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=weilin.wang@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