[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180706055115.we4yegemiiqe4zdm@salmiak>
Date: Fri, 6 Jul 2018 06:51:16 +0100
From: Mark Rutland <mark.rutland@....com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
will.deacon@....com, andy.shevchenko@...il.com, arnd@...db.de,
aryabinin@...tuozzo.com, boqun.feng@...il.com,
catalin.marinas@....com, dvyukov@...gle.com, glider@...gle.com,
hpa@...or.com, linuxdrivers@...otech.com, mingo@...nel.org,
mingo@...hat.com, parri.andrea@...il.com, peter@...leysoftware.com,
tglx@...utronix.de
Subject: Re: [PATCHv3 08/12] atomics: switch to generated fallbacks
On Thu, Jul 05, 2018 at 07:23:06PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 05, 2018 at 05:40:49PM +0100, Mark Rutland wrote:
>
> > * The fallbacks are not expected to change very often, and are not
> > affected by machine details or configuration options, so regenerating
> > them for *every* build is somewhat wasteful.
>
> Except of course, your last patch in this series now does exactly that
> :-)
Second-last, but agreed. ;)
I'll reword this to:
* The fallbacks are not affected by machine details or configuration options,
so it is not necessary to regenerate them to take these into account.
Thanks,
Mark.
Powered by blists - more mailing lists