2013/3/26 Ingo Molnar <mi...@kernel.org>: > > * Frederic Weisbecker <fweis...@gmail.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 ...
Right. So indeed the feature is not implemented yet in tip:timers/nohz, ie: the tick won't be stopped. But the current halfway state is not supposed to break existing things. But I agree. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/