All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	LKML <Linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>,
	kan.liang@intel.com, "Jin, Yao" <yao.jin@intel.com>
Subject: Re: [PATCH 0/2] Update CascadelakeX and SkylakeX events list
Date: Tue, 16 Jun 2020 14:27:40 +0800	[thread overview]
Message-ID: <c7edd282-f58a-4efe-5961-6c1369b6b77b@linux.intel.com> (raw)
In-Reply-To: <CAP-5=fW3OCuVkQ8csYfHXj5c_pCSY5-6vDrj2r=MNDZmpo0f8g@mail.gmail.com>

Hi Ian, Arnaldo,

On 6/16/2020 2:16 PM, Ian Rogers wrote:
> On Mon, Jun 15, 2020 at 6:00 PM Jin, Yao <yao.jin@linux.intel.com> wrote:
>>
>> 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.
> 
> Hi Jin Yao,
> 
> could you rebase this on Arnaldo's tmp.perf/core tree?
> https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/log/?h=tmp.perf/core
> I tried using git am but get:
> Applying: perf vendor events: Update CascadelakeX events to v1.08
> error: patch fragment without header at line 279: @@ -213,14 +220,14 @@
> error: could not build fake ancestor
> Patch failed at 0001 perf vendor events: Update CascadelakeX events to v1.08
> 
> Thanks,
> Ian
> 

The patchset are applied OK on perf/core branch.

As far as I understand, the patch for posting should be based on perf/core branch, is it right?

Thanks
Jin Yao

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

  reply	other threads:[~2020-06-16  6:27 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 ` [PATCH 0/2] Update CascadelakeX and SkylakeX events list Jin, Yao
2020-06-16  6:16   ` Ian Rogers
2020-06-16  6:27     ` Jin, Yao [this message]
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=c7edd282-f58a-4efe-5961-6c1369b6b77b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.