From: Namhyung Kim <namhyung@kernel.org>
To: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
Cc: Chun-Tse Shao <ctshao@google.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
adrian.hunter@intel.com, james.clark@linaro.org,
afaerber@suse.de, mani@kernel.org, thomas.falcon@intel.com,
irogers@google.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, perry.taylor@intel.com
Subject: Re: [PATCH v1 0/12] perf vendor events intel: update
Date: Tue, 14 Jul 2026 10:37:23 -0700 [thread overview]
Message-ID: <alZz0xH7h98uzLo1@google.com> (raw)
In-Reply-To: <2e182845-6771-473c-a82a-bf96953b458e@linux.intel.com>
Hello,
On Tue, Jul 14, 2026 at 01:21:46PM +0800, Mi, Dapeng wrote:
> The patchset looks good to me. But It depends on this patch
> https://lore.kernel.org/all/20260708053226.3776183-1-dapeng1.mi@linux.intel.com/.
> Without this patch, the building on NVL would fail. Thanks.
I'll pick that up too.
>
> Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
Thanks for the review!
Namhyung
>
> On 7/14/2026 2:17 AM, Chun-Tse Shao wrote:
> > Sync the Linux kernel perf PMU events with the latest upstream Intel
> > perfmon repository.
> >
> > This patchset includes event and metric updates for Alder Lake, Alder
> > Lake N, Arrow Lake, Clearwater Forest, Emerald Rapids (including IIO
> > bandwidth metrics), Grand Ridge, Granite Rapids, Lunar Lake, Meteor
> > Lake, Panther Lake, and Sierra Forest, as well as adding initial event
> > support for Nova Lake v1.00.
> >
> > Chun-Tse Shao (12):
> > perf vendor events intel: Update alderlake events from 1.39 to 1.40
> > perf vendor events intel: Update alderlaken events from 1.39 to 1.40
> > perf vendor events intel: Update arrowlake events from 1.19 to 1.20
> > perf vendor events intel: Update clearwaterforest events from 1.02 to
> > 1.04
> > perf vendor events intel: Update grandridge events from 1.12 to 1.13
> > perf vendor events intel: Update graniterapids events from 1.19 to
> > 1.20
> > perf vendor events intel: Update lunarlake events from 1.25 to 1.26
> > perf vendor events intel: Update meteorlake events from 1.21 to 1.22
> > perf vendor events intel: Add novalake v1.00 events
> > perf vendor events intel: Update pantherlake events from 1.06 to 1.07
> > perf vendor events intel: Update sierraforest events from 1.17 to 1.18
> > perf vendor events intel: Update emeraldrapids metrics
> >
> > .../arch/x86/alderlake/adl-metrics.json | 80 +-
> > .../pmu-events/arch/x86/alderlake/cache.json | 36 +
> > .../arch/x86/alderlake/metricgroups.json | 2 +-
> > .../arch/x86/alderlake/pipeline.json | 6 +-
> > .../pmu-events/arch/x86/alderlaken/cache.json | 32 +
> > .../arch/x86/arrowlake/arl-metrics.json | 152 +-
> > .../arch/x86/arrowlake/metricgroups.json | 2 +-
> > .../arch/x86/arrowlake/pipeline.json | 2 +-
> > .../arch/x86/arrowlake/uncore-memory.json | 84 +-
> > .../arch/x86/clearwaterforest/memory.json | 33 +
> > .../arch/x86/clearwaterforest/pipeline.json | 19 +
> > .../clearwaterforest/uncore-interconnect.json | 10 +
> > .../x86/clearwaterforest/uncore-memory.json | 2 +-
> > .../arch/x86/emeraldrapids/emr-metrics.json | 135 +-
> > .../arch/x86/emeraldrapids/metricgroups.json | 2 +-
> > .../pmu-events/arch/x86/grandridge/cache.json | 25 +
> > .../arch/x86/grandridge/counter.json | 42 -
> > .../arch/x86/grandridge/floating-point.json | 56 +
> > .../arch/x86/grandridge/memory.json | 57 +
> > .../arch/x86/grandridge/pipeline.json | 140 ++
> > .../arch/x86/grandridge/uncore-memory.json | 2 +-
> > .../arch/x86/grandridge/virtual-memory.json | 8 +
> > .../arch/x86/graniterapids/gnr-metrics.json | 102 +-
> > .../arch/x86/graniterapids/metricgroups.json | 2 +-
> > .../arch/x86/graniterapids/pipeline.json | 2 +-
> > .../arch/x86/lunarlake/lnl-metrics.json | 142 +-
> > .../arch/x86/lunarlake/metricgroups.json | 2 +-
> > .../arch/x86/lunarlake/pipeline.json | 2 +-
> > tools/perf/pmu-events/arch/x86/mapfile.csv | 21 +-
> > .../pmu-events/arch/x86/meteorlake/cache.json | 11 +-
> > .../arch/x86/meteorlake/metricgroups.json | 2 +-
> > .../arch/x86/meteorlake/mtl-metrics.json | 88 +-
> > .../arch/x86/meteorlake/pipeline.json | 4 +-
> > .../arch/x86/meteorlake/uncore-memory.json | 84 +-
> > .../pmu-events/arch/x86/novalake/cache.json | 749 +++++++
> > .../pmu-events/arch/x86/novalake/counter.json | 17 +
> > .../arch/x86/novalake/floating-point.json | 452 ++++
> > .../arch/x86/novalake/frontend.json | 600 +++++
> > .../pmu-events/arch/x86/novalake/memory.json | 299 +++
> > .../pmu-events/arch/x86/novalake/other.json | 144 ++
> > .../arch/x86/novalake/pipeline.json | 1976 +++++++++++++++++
> > .../arch/x86/novalake/uncore-memory.json | 42 +
> > .../arch/x86/novalake/virtual-memory.json | 338 +++
> > .../arch/x86/pantherlake/pipeline.json | 2 +-
> > .../arch/x86/sierraforest/counter.json | 77 -
> > .../x86/sierraforest/uncore-interconnect.json | 10 +
> > .../arch/x86/sierraforest/uncore-memory.json | 2 +-
> > 47 files changed, 5615 insertions(+), 482 deletions(-)
> > delete mode 100644 tools/perf/pmu-events/arch/x86/grandridge/counter.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/cache.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/counter.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/floating-point.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/frontend.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/memory.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/other.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/pipeline.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/uncore-memory.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/novalake/virtual-memory.json
> > delete mode 100644 tools/perf/pmu-events/arch/x86/sierraforest/counter.json
> >
next prev parent reply other threads:[~2026-07-14 17:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 18:17 [PATCH v1 0/12] perf vendor events intel: update Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 01/12] perf vendor events intel: Update alderlake events from 1.39 to 1.40 Chun-Tse Shao
2026-07-13 18:27 ` sashiko-bot
2026-07-13 18:17 ` [PATCH v1 02/12] perf vendor events intel: Update alderlaken " Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 03/12] perf vendor events intel: Update arrowlake events from 1.19 to 1.20 Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 04/12] perf vendor events intel: Update clearwaterforest events from 1.02 to 1.04 Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 05/12] perf vendor events intel: Update grandridge events from 1.12 to 1.13 Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 06/12] perf vendor events intel: Update graniterapids events from 1.19 to 1.20 Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 07/12] perf vendor events intel: Update lunarlake events from 1.25 to 1.26 Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 08/12] perf vendor events intel: Update meteorlake events from 1.21 to 1.22 Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 09/12] perf vendor events intel: Add novalake v1.00 events Chun-Tse Shao
2026-07-13 18:31 ` sashiko-bot
2026-07-13 18:17 ` [PATCH v1 10/12] perf vendor events intel: Update pantherlake events from 1.06 to 1.07 Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 11/12] perf vendor events intel: Update sierraforest events from 1.17 to 1.18 Chun-Tse Shao
2026-07-13 18:17 ` [PATCH v1 12/12] perf vendor events intel: Update emeraldrapids metrics Chun-Tse Shao
2026-07-14 5:21 ` [PATCH v1 0/12] perf vendor events intel: update Mi, Dapeng
2026-07-14 17:37 ` Namhyung Kim [this message]
2026-07-14 20:42 ` Chun-Tse Shao
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=alZz0xH7h98uzLo1@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=ctshao@google.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mingo@redhat.com \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=thomas.falcon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.