[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160429091859.GE3448@twins.programming.kicks-ass.net>
Date: Fri, 29 Apr 2016 11:18:59 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: David Carrillo-Cisneros <davidcc@...gle.com>
Cc: Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
Matt Fleming <matt.fleming@...el.com>,
Tony Luck <tony.luck@...el.com>,
Stephane Eranian <eranian@...gle.com>,
Paul Turner <pjt@...gle.com>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/32] perf/x86/intel/cqm: prepare for next patches
On Thu, Apr 28, 2016 at 09:43:14PM -0700, David Carrillo-Cisneros wrote:
> Move code around, delete unnecesary code and do some renaming in
> in order to increase readibility of next patches. Create cqm.h file.
*sigh*, this is a royal pain in the backside to review.
Please just completely wipe the old driver in patch 1, preserve
_nothing_.
Then start adding bits back, in gradual coherent pieces. Like that msr
write optimization you need new hooks for, that should be a patch doing
just that, optimize, it should not introduce new functionality etc..
This piecewise removal of small bits makes it entirely hard to see the
complete picture of what is introduced here.
Powered by blists - more mailing lists