lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 17 Jul 2020 14:06:51 +0800
From:   "Jin, Yao" <>
To:     Arnaldo Carvalho de Melo <>
Cc:     Ian Rogers <>, Jiri Olsa <>,
        Peter Zijlstra <>,
        Ingo Molnar <>,
        Alexander Shishkin <>,
        LKML <>,
        Andi Kleen <>,,
        "Jin, Yao" <>
Subject: Re: [PATCH 0/2] Update CascadelakeX and SkylakeX events list


On 6/17/2020 3:38 AM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jun 16, 2020 at 02:27:40PM +0800, Jin, Yao escreveu:
>> On 6/16/2020 2:16 PM, Ian Rogers wrote:
>>> On Mon, Jun 15, 2020 at 6:00 PM Jin, Yao <> wrote:
>>>> Can I get an ACK for this patchset?
>>>> 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.
>>> could you rebase this on Arnaldo's tmp.perf/core tree?
>>> 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?
> Sorry, I've been testing with using tmp.perf/core as a way to more
> quickly make available what I've processed, before I test it thoroughly
> both with container builds and with manual testing, so the bleeding edge
> is there, perf/core becoming a bit more stable, as I'll try not to
> rebase it like before.
> - Arnaldo

Can this event update be accepted?

Jin Yao

Powered by blists - more mailing lists