Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Chun-Tse Shao <ctshao@google.com>,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	namhyung@kernel.org
Cc: alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	irogers@google.com, adrian.hunter@intel.com,
	james.clark@linaro.org, afaerber@suse.de, mani@kernel.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-actions@lists.infradead.org
Subject: Re: [PATCH v1 0/6] perf vendor events intel: update
Date: Mon, 15 Jun 2026 09:32:36 +0800	[thread overview]
Message-ID: <0b6d58d5-f802-47dc-ae71-31c45184b738@linux.intel.com> (raw)
In-Reply-To: <20260609215046.2391903-1-ctshao@google.com>

LGTM. Thanks.

Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>

On 6/10/2026 5:50 AM, Chun-Tse Shao wrote:
> Sync with the latest perfmon events from:
> https://github.com/intel/perfmon
> by running the script:
> https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
> and copying the resulting json and mapfile.csv changes into the perf
> tree.
>
> Chun-Tse Shao (6):
>   perf vendor events intel: Update arrowlake events from 1.17 to 1.19
>   perf vendor events intel: Update emeraldrapids events from 1.23 to
>     1.24
>   perf vendor events intel: Update graniterapids events from 1.18 to
>     1.19
>   perf vendor events intel: Update lunarlake events from 1.22 to 1.25
>   perf vendor events intel: Update pantherlake events from 1.05 to 1.06
>   perf vendor events intel: Update tigerlake events from 1.18 to 1.19
>
>  .../pmu-events/arch/x86/arrowlake/cache.json  |  30 ++-
>  .../arch/x86/arrowlake/floating-point.json    |  45 ++++
>  .../pmu-events/arch/x86/arrowlake/memory.json |  18 ++
>  .../arch/x86/arrowlake/pipeline.json          | 129 +++++++++-
>  .../arch/x86/emeraldrapids/cache.json         |   9 +
>  .../graniterapids/uncore-interconnect.json    |  10 +
>  .../arch/x86/graniterapids/uncore-memory.json |   2 +-
>  .../pmu-events/arch/x86/lunarlake/cache.json  |   2 +-
>  .../arch/x86/lunarlake/pipeline.json          |  27 ++-
>  .../arch/x86/lunarlake/uncore-memory.json     | 208 ++++++++++++++++-
>  tools/perf/pmu-events/arch/x86/mapfile.csv    |  12 +-
>  .../arch/x86/pantherlake/counter.json         |   5 +
>  .../arch/x86/pantherlake/pipeline.json        |  29 ++-
>  .../x86/pantherlake/uncore-interconnect.json  |  10 +
>  .../arch/x86/pantherlake/uncore-memory.json   | 221 +++++++++++++++++-
>  15 files changed, 728 insertions(+), 29 deletions(-)
>  create mode 100644 tools/perf/pmu-events/arch/x86/pantherlake/uncore-interconnect.json
>


  parent reply	other threads:[~2026-06-15  1:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 21:50 [PATCH v1 0/6] perf vendor events intel: update Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 1/6] perf vendor events intel: Update arrowlake events from 1.17 to 1.19 Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 2/6] perf vendor events intel: Update emeraldrapids events from 1.23 to 1.24 Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 3/6] perf vendor events intel: Update graniterapids events from 1.18 to 1.19 Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 4/6] perf vendor events intel: Update lunarlake events from 1.22 to 1.25 Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 5/6] perf vendor events intel: Update pantherlake events from 1.05 to 1.06 Chun-Tse Shao
2026-06-09 21:50 ` [PATCH v1 6/6] perf vendor events intel: Update tigerlake events from 1.18 to 1.19 Chun-Tse Shao
2026-06-15  1:32 ` Mi, Dapeng [this message]
2026-06-15 15:37   ` [PATCH v1 0/6] perf vendor events intel: update 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=0b6d58d5-f802-47dc-ae71-31c45184b738@linux.intel.com \
    --to=dapeng1.mi@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=afaerber@suse.de \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ctshao@google.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-actions@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /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