linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jin Yao <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, yao.jin@intel.com, irogers@google.com,
	Jin Yao <yao.jin@linux.intel.com>
Subject: [PATCH v2 0/2] perf: Update CascadelakeX and SkylakeX events list
Date: Tue, 22 Sep 2020 11:19:16 +0800	[thread overview]
Message-ID: <20200922031918.3723-1-yao.jin@linux.intel.com> (raw)

This patchset updates CascadelakeX events to v1.08 and
updates SkylakeX events to v1.21.

The events have been tested on CascadelakeX and SkylakeX
servers with latest perf/core branch.

The first version was posted a few months ago and now just
resend the patchset with minor update.

 v2:
   - Change 'MB/sec' to 'MB' in UNC_M_PMM_BANDWIDTH.

Jin Yao (2):
  perf vendor events: Update CascadelakeX events to v1.08
  perf vendor events: Update SkylakeX events to v1.21

 .../arch/x86/cascadelakex/cache.json          |   28 +-
 .../arch/x86/cascadelakex/clx-metrics.json    |  153 +-
 .../arch/x86/cascadelakex/frontend.json       |   34 +
 .../arch/x86/cascadelakex/memory.json         |  704 ++---
 .../arch/x86/cascadelakex/other.json          | 1100 ++++----
 .../arch/x86/cascadelakex/pipeline.json       |   10 -
 .../arch/x86/cascadelakex/uncore-memory.json  |   12 +-
 .../arch/x86/cascadelakex/uncore-other.json   |   21 +
 .../pmu-events/arch/x86/skylakex/cache.json   | 2348 +++++++++--------
 .../arch/x86/skylakex/floating-point.json     |   96 +-
 .../arch/x86/skylakex/frontend.json           |  656 ++---
 .../pmu-events/arch/x86/skylakex/memory.json  | 1977 +++++++-------
 .../pmu-events/arch/x86/skylakex/other.json   |  172 +-
 .../arch/x86/skylakex/pipeline.json           | 1206 +++++----
 .../arch/x86/skylakex/skx-metrics.json        |  141 +-
 .../arch/x86/skylakex/uncore-memory.json      |   26 +-
 .../arch/x86/skylakex/uncore-other.json       |  730 ++++-
 .../arch/x86/skylakex/virtual-memory.json     |  358 +--
 18 files changed, 5204 insertions(+), 4568 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-09-22  3:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  3:19 Jin Yao [this message]
2020-09-22 19:22 ` [PATCH v2 0/2] perf: Update CascadelakeX and SkylakeX events list Andi Kleen
     [not found] ` <20200922031918.3723-2-yao.jin@linux.intel.com>
2020-09-22 19:42   ` [PATCH v2 1/2] perf vendor events: Update CascadelakeX events to v1.08 Arnaldo Carvalho de Melo
     [not found]     ` <4db737f2-0705-5183-6971-9031acfd123b@linux.intel.com>
2020-09-23 21:04       ` Ian Rogers
2020-09-25 18:05       ` Arnaldo Carvalho de Melo
2020-09-25 18:36         ` Andi Kleen
2020-09-25 19:21           ` Arnaldo Carvalho de Melo
2020-09-25 19:43           ` Ian Rogers
2020-09-25 20:23         ` Konstantin Ryabitsev
2020-10-09  3:45         ` Jin, Yao
2020-09-28 11:47       ` 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=20200922031918.3723-1-yao.jin@linux.intel.com \
    --to=yao.jin@linux.intel.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@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;
as well as URLs for NNTP newsgroup(s).