From: Xing Zhengjun <zhengjun.xing@linux.intel.com>
To: Ian Rogers <irogers@google.com>
Cc: acme@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@intel.com, jolsa@kernel.org,
namhyung@kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, ak@linux.intel.com,
kan.liang@linux.intel.com
Subject: Re: [PATCH 00/11] Add generated latest Intel events and metrics
Date: Sun, 14 Aug 2022 00:52:04 +0800 [thread overview]
Message-ID: <b118ec12-6b51-3b86-22b2-c7689e0f91d8@linux.intel.com> (raw)
In-Reply-To: <CAP-5=fVTOvY0_3PxrzP28iFn0FtDgQE34qJ4_6+fD-TQohCFQQ@mail.gmail.com>
Hi Ian,
On 8/13/2022 4:53 AM, Ian Rogers wrote:
> On Fri, Aug 12, 2022 at 1:51 AM <zhengjun.xing@linux.intel.com
> <mailto:zhengjun.xing@linux.intel.com>> wrote:
>
> From: Zhengjun Xing <zhengjun.xing@linux.intel.com
> <mailto:zhengjun.xing@linux.intel.com>>
>
> The goal of this patch series is to align the json events for Intel
> platforms with those generated by:
> https://github.com/intel/event-converter-for-linux-perf/blob/master/download_and_gen.py
> <https://github.com/intel/event-converter-for-linux-perf/blob/master/download_and_gen.py>
> This script takes the latest event json and TMA metrics from:
> https://download.01.org/perfmon/ <https://download.01.org/perfmon/>
> and adds to these metrics, in
> particular uncore ones, from:
> https://github.com/intel/perfmon-metrics
> <https://github.com/intel/perfmon-metrics>
>
> Compared to the previous json, the major changes are:
> - Add new metrics “UNCORE_FREQ” for Linux perf,this new metric can
> be added to all platforms that have Sockets_CLKS.
> - Remove duplicated uncore events.
> - the inclusion of previously ungenerated and experimental uncore
> events.
>
> Zhengjun Xing (11):
> perf vendor events: Update metrics for broadwellde
> perf vendor events: Update events and metrics for broadwellx
> perf vendor events: Update events and metrics for cascadelakex
> perf vendor events: Update events and metrics for haswellx
> perf vendor events: Update events and metrics for icelakex
> perf vendor events: Update metrics for ivytown
> perf vendor events: Update metrics for jaketown
> perf vendor events: Update events for knightslanding
> perf vendor events: Update metrics for sapphirerapids
> perf vendor events: Update events and metrics for skylakex
> perf vendor events: Update events for snowridgex
>
>
> Tested-by: Ian Rogers <irogers@google.com <mailto:irogers@google.com>>
>
Thanks.
> Thanks,
> Ian
>
> .../arch/x86/broadwellde/bdwde-metrics.json | 6 +
> .../arch/x86/broadwellx/bdx-metrics.json | 6 +
> .../arch/x86/broadwellx/uncore-cache.json | 163 +-
> .../arch/x86/cascadelakex/clx-metrics.json | 6 +
> .../arch/x86/cascadelakex/uncore-memory.json | 4424 +-
> .../arch/x86/cascadelakex/uncore-other.json | 23162 +++++++++-
> .../arch/x86/cascadelakex/uncore-power.json | 201 +
> .../arch/x86/haswellx/hsx-metrics.json | 411 +-
> .../arch/x86/haswellx/uncore-cache.json | 173 +-
> .../arch/x86/icelakex/icx-metrics.json | 6 +
> .../arch/x86/icelakex/uncore-memory.json | 1523 +
> .../arch/x86/icelakex/uncore-other.json | 38506 +++++++++++++++-
> .../arch/x86/icelakex/uncore-power.json | 225 +
> .../arch/x86/ivytown/ivt-metrics.json | 6 +
> .../arch/x86/jaketown/jkt-metrics.json | 6 +
> .../arch/x86/knightslanding/uncore-other.json | 213 +
> .../arch/x86/sapphirerapids/spr-metrics.json | 6 +
> .../arch/x86/skylakex/skx-metrics.json | 6 +
> .../arch/x86/skylakex/uncore-memory.json | 3566 +-
> .../arch/x86/skylakex/uncore-other.json | 23442 +++++++++-
> .../arch/x86/skylakex/uncore-power.json | 201 +
> .../arch/x86/snowridgex/uncore-other.json | 111 +-
> 22 files changed, 91393 insertions(+), 4976 deletions(-)
> create mode 100644
> tools/perf/pmu-events/arch/x86/cascadelakex/uncore-power.json
> create mode 100644
> tools/perf/pmu-events/arch/x86/skylakex/uncore-power.json
>
> --
> 2.25.1
>
--
Zhengjun Xing
next prev parent reply other threads:[~2022-08-13 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 8:52 [PATCH 00/11] Add generated latest Intel events and metrics zhengjun.xing
2022-08-12 8:52 ` [PATCH 01/11] perf vendor events: Update metrics for broadwellde zhengjun.xing
2022-08-12 8:52 ` [PATCH 02/11] perf vendor events: Update events and metrics for broadwellx zhengjun.xing
2022-08-12 8:52 ` [PATCH 04/11] perf vendor events: Update events and metrics for haswellx zhengjun.xing
2022-08-12 8:52 ` [PATCH 06/11] perf vendor events: Update metrics for ivytown zhengjun.xing
2022-08-12 8:52 ` [PATCH 07/11] perf vendor events: Update metrics for jaketown zhengjun.xing
2022-08-12 8:52 ` [PATCH 08/11] perf vendor events: Update events for knightslanding zhengjun.xing
2022-08-12 8:52 ` [PATCH 09/11] perf vendor events: Update metrics for sapphirerapids zhengjun.xing
2022-08-12 8:52 ` [PATCH 11/11] perf vendor events: Update events for snowridgex zhengjun.xing
[not found] ` <CAP-5=fVTOvY0_3PxrzP28iFn0FtDgQE34qJ4_6+fD-TQohCFQQ@mail.gmail.com>
2022-08-13 16:52 ` Xing Zhengjun [this message]
2022-08-13 18:08 ` [PATCH 00/11] Add generated latest Intel events and metrics 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=b118ec12-6b51-3b86-22b2-c7689e0f91d8@linux.intel.com \
--to=zhengjun.xing@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@intel.com \
--cc=irogers@google.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=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;
as well as URLs for NNTP newsgroup(s).