[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130326081527.GA27128@gmail.com>
Date: Tue, 26 Mar 2013 09:15:27 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Chris Metcalf <cmetcalf@...era.com>,
Christoph Lameter <cl@...ux.com>,
Geoff Levand <geoff@...radead.org>,
Gilad Ben Yossef <gilad@...yossef.com>,
Hakan Akkan <hakanakkan@...il.com>,
Kevin Hilman <khilman@...aro.org>,
Li Zhong <zhong@...ux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@....com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [GIT PULL] nohz: Full dynticks base interface
* Frederic Weisbecker <fweisbec@...il.com> wrote:
> > That way I will be able to test it automatically via randconfig and
> > such.
>
> Sure, I'm adding such an option.
>
> > My next question/request after that would be: could we make sure that
> > enabling this option does not break any applications or kernel
> > functionality, ASAP? Once that is offered, it becomes pushable to
> > v3.10 I think.
>
> So that's already the case. I'm careful that, as we iterate, the changes
> aren't supposed to break something in the middle. the final code that
> eventually shuts the tick down should be the last one in the series:
> once we know it is safe to do so.
I mean, with the .config (or boot) option enabled, with tip:timers/nohz
as-is, will everything work? We cannot push a feature to Linus that
doesn't work reliably when enabled ...
Thanks,
Ingo
--
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