linux-kernel - Re: Fwd: [V6 00/11] perf: New conditional branch filter

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]

Message-ID: <1400733004.14864.9.camel@concordia>
Date:	Thu, 22 May 2014 14:30:04 +1000
From:	Michael Ellerman <mpe@...erman.id.au>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Anshuman Khandual <khandual@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: Fwd: [V6 00/11] perf: New conditional branch filter

On Wed, 2014-05-21 at 14:01 +0200, Peter Zijlstra wrote:
> On Wed, May 21, 2014 at 04:09:55PM +0530, Anshuman Khandual wrote:
> > On 05/21/2014 02:53 PM, Peter Zijlstra wrote:
> > > On Wed, May 21, 2014 at 02:41:58PM +0530, Anshuman Khandual wrote:
> > >> Hello Peter/Ingo,
> > >>
> > >> Would you please consider reviewing the first four patches in this patch series
> > >> which changes the generic perf kernel and perf tools code. Andi Kleen and Stephane
> > >> Eranian have already reviewed these changes. The rest of the patch series is related
> > >> to powerpc and being reviewed by Michael Ellerman/Ben.
> > >>
> > > 
> > > If they land in my inbox I might have a look.
> > > 
> > 
> > Sent.
> 
> Thanks, they look fine to me, although 1/x can use a lightly longer
> changelog, making it explicit its a filter for conditional branches.
> 
> How do people want this routed? Should I take all patches through tip,
> or do I ask Ingo to create a special perf/cond branch which includes the
> first 4 patches which can be merged into whatever ppc branch and the
> rest then go on top in the ppc tree?

Hi Peter,

Can you take just the first 4 in your tree please. I asked Anshuman to just
send those 4 but he & I seem to have miscommunicated on that.

We only depend on patch 1 in order for the powerpc parts to build, so I think
we'll just merge that into the powerpc tree and it should merge fine when it
hits next.

cheers


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/