LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2 0/2] perf vendor events intel: Add core events and metrics for Elkhartlake
Date: Mon, 2 Aug 2021 09:58:04 -0300	[thread overview]
Message-ID: <YQfr3NFtOH3tu5ZV@kernel.org> (raw)
In-Reply-To: <20210802053440.21035-1-yao.jin@linux.intel.com>

Em Mon, Aug 02, 2021 at 01:34:38PM +0800, Jin Yao escreveu:
> Add JSON events and metrics for Elkhartlake to perf.
> 
> Based on JSON list v1.02:
> 
> https://download.01.org/perfmon/EHL/

Thanks, applied.

- Arnaldo

 
> v2:
> ---
> Based on JSON list v1.02.
> Patchset is based on tmp.perf/core branch.
> 
> v1:
> ---
> Based on JSON list v1.01
> 
> Jin Yao (2):
>   perf vendor events intel: Add core event list for Elkhartlake
>   perf vendor events intel: Add basic metrics for Elkhartlake
> 
>  .../arch/x86/elkhartlake/cache.json           | 226 ++++++++++
>  .../arch/x86/elkhartlake/ehl-metrics.json     |  57 +++
>  .../arch/x86/elkhartlake/floating-point.json  |  24 +
>  .../arch/x86/elkhartlake/frontend.json        |  93 ++++
>  .../arch/x86/elkhartlake/memory.json          |  86 ++++
>  .../arch/x86/elkhartlake/other.json           | 424 ++++++++++++++++++
>  .../arch/x86/elkhartlake/pipeline.json        | 278 ++++++++++++
>  .../arch/x86/elkhartlake/virtual-memory.json  | 273 +++++++++++
>  tools/perf/pmu-events/arch/x86/mapfile.csv    |   1 +
>  9 files changed, 1462 insertions(+)
>  create mode 100644 tools/perf/pmu-events/arch/x86/elkhartlake/cache.json
>  create mode 100644 tools/perf/pmu-events/arch/x86/elkhartlake/ehl-metrics.json
>  create mode 100644 tools/perf/pmu-events/arch/x86/elkhartlake/floating-point.json
>  create mode 100644 tools/perf/pmu-events/arch/x86/elkhartlake/frontend.json
>  create mode 100644 tools/perf/pmu-events/arch/x86/elkhartlake/memory.json
>  create mode 100644 tools/perf/pmu-events/arch/x86/elkhartlake/other.json
>  create mode 100644 tools/perf/pmu-events/arch/x86/elkhartlake/pipeline.json
>  create mode 100644 tools/perf/pmu-events/arch/x86/elkhartlake/virtual-memory.json
> 
> -- 
> 2.17.1
> 

-- 

- Arnaldo

      parent reply	other threads:[~2021-08-02 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  5:34 Jin Yao
2021-08-02  5:34 ` [PATCH v2 1/2] perf vendor events intel: Add core event list " Jin Yao
2021-08-02  5:34 ` [PATCH v2 2/2] perf vendor events intel: Add basic metrics " Jin Yao
2021-08-02 12:58 ` Arnaldo Carvalho de Melo [this message]

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=YQfr3NFtOH3tu5ZV@kernel.org \
    --to=acme@kernel.org \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.com \
    --subject='Re: [PATCH v2 0/2] perf vendor events intel: Add core events and metrics for Elkhartlake' \
    /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

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).