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
Subject: Re: [PATCH 0/2] Update CascadelakeX and SkylakeX events list
Date: Tue, 16 Jun 2020 08:59:59 +0800	[thread overview]
Message-ID: <911b4132-d1a1-f3c4-a2ed-2fcfe9a28fc6@linux.intel.com> (raw)
In-Reply-To: <20200603021818.27028-1-yao.jin@linux.intel.com>

Hi Andi,

Can I get an ACK for this patchset?

Thanks
Jin Yao

On 6/3/2020 10:18 AM, Jin Yao wrote:
> 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.
> 
> 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-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 +--
>   17 files changed, 5198 insertions(+), 4562 deletions(-)
> 

  parent reply	other threads:[~2020-06-16  1:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  2:18 [PATCH 0/2] Update CascadelakeX and SkylakeX events list Jin Yao
2020-06-03  2:18 ` [PATCH 1/2] perf vendor events: Update CascadelakeX events to v1.08 Jin Yao
2020-06-03  2:18 ` [PATCH 2/2] perf vendor events: Update SkylakeX events to v1.21 Jin Yao
2020-06-16  0:59 ` Jin, Yao [this message]
2020-06-16  6:16   ` [PATCH 0/2] Update CascadelakeX and SkylakeX events list Ian Rogers
2020-06-16  6:27     ` Jin, Yao
2020-06-16 19:38       ` Arnaldo Carvalho de Melo
2020-07-17  6:06         ` Jin, Yao
2020-09-07  8:01           ` Jin, Yao
2020-09-18  1:21             ` Jin, Yao
     [not found]               ` <CAP-5=fX7faeJWqDwjzOA51ipfJufYDxh=ErF0tiN18y2bBx9dA@mail.gmail.com>
2020-09-18  2:23                 ` Jin, Yao

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=911b4132-d1a1-f3c4-a2ed-2fcfe9a28fc6@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=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).