lists.openwall.net   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  linux-cve-announce  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:   Tue, 16 Jun 2020 16:38:56 -0300
From:   Arnaldo Carvalho de Melo <acme@...nel.org>
To:     "Jin, Yao" <yao.jin@...ux.intel.com>
Cc:     Ian Rogers <irogers@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        LKML <Linux-kernel@...r.kernel.org>,
        Andi Kleen <ak@...ux.intel.com>, kan.liang@...el.com,
        "Jin, Yao" <yao.jin@...el.com>
Subject: Re: [PATCH 0/2] Update CascadelakeX and SkylakeX events list

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 <yao.jin@...ux.intel.com> 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?
> > 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?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ