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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 29 Jul 2014 16:41:25 +0200
From:	Stephane Eranian <eranian@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	"Yan, Zheng" <zheng.z.yan@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH] perf/x86/uncore: split Intel uncore driver to smaller files

On Mon, Jul 28, 2014 at 10:53 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Mon, Jul 28, 2014 at 04:05:45PM +0800, Yan, Zheng wrote:
>> On 07/28/2014 03:56 PM, Peter Zijlstra wrote:
>> > On Fri, Jul 25, 2014 at 04:40:55PM +0800, Yan, Zheng wrote:
>> >> split Intel uncore driver into four files:
>> >>  - perf_event_intel_uncore.c: general functions of Intel uncore driver.
>> >>  - perf_event_intel_uncore_nhmex.c: hardware specific code for
>> >>    Nehalem-EX/Westmere-EX
>> >>  - perf_event_intel_uncore_snb.c: hardware specific code for
>> >>    Nehalem/SandBridge/Haswell
>> >>  - perf_event_intel_uncore_snbep.c: hardware specific code for
>> >>    SandyBridge-EP/IvyTown uncore
>> >
>> > Did not apply properly to tip/master, also can you do that in 3 patches?
>> >
>>
>> the patch is based on tip/perf/core
>
> Hmm, that should be good enough, didn't want to apply though, gave a
> massive rej.
>
>> > One breaking out the nhm/wsm-ex part, one breaking out the
>> > nhm/wsm/snb/ivb/hsw bits, and one for the snb/ivb-ep bits?
>> >
I agree with Peter here.

>> will do
>
> Thanks!
--
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/

Powered by blists - more mailing lists