linux-kernel - Re: [PATCH v7 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads

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:   Thu, 6 Sep 2018 10:14:38 +0200
From:   Jiri Olsa <jolsa@...hat.com>
To:     Alexey Budankov <alexey.budankov@...ux.intel.com>
Cc:     Arnaldo Carvalho de Melo <acme@...nel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Namhyung Kim <namhyung@...nel.org>,
        Andi Kleen <ak@...ux.intel.com>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v7 0/2]: perf: reduce data loss when profiling highly
 parallel CPU bound workloads

On Thu, Sep 06, 2018 at 09:03:17AM +0300, Alexey Budankov wrote:
> Hi,
> 
> On 05.09.2018 21:51, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Sep 05, 2018 at 08:37:32PM +0300, Alexey Budankov escreveu:
> >> On 05.09.2018 14:28, Jiri Olsa wrote:
> >>> can't apply this version on Arnaldo's perf/core...
> >  
> >> my git remote -v
> >  
> >> origin	git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (fetch)
> >> origin	git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (push)
> >  
> >> branch is perf/core, according to MAINTAINERS content.
> >  
> >> What is Arnaldo's perf/core? This one?
> >  
> >> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
> >  
> >> and branch is perf/core?
> > 
> > yes.
> 
> Is this the actual one for the tool development? Am I missing something?

yep, Arnaldo takes all and pushes his perf/core to Ingo
it's better to always rebase to it

thanks,
jirka