lkml.org 
[lkml]   [2014]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [tip:timers/nohz] nohz: Move full nohz kick to its own IPI

* Frederic Weisbecker <fweisbec@gmail.com> wrote:

> On Wed, May 07, 2014 at 09:07:14PM +0200, Ingo Molnar wrote:
> >
> > * Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > > On Wed, May 07, 2014 at 06:05:08PM +0200, Frederic Weisbecker wrote:
> > > > So we can as well zap these commits and replace them with the irq_work_on()
> > > > conversion (still preparing that).
> > >
> > > I hear you, but I think Ingo doesn't want to rebase the tree because its
> > > public, but maybe he can make an exception..
> >
> > Since tip:timers/nohz only contains these commits:
> >
> > fc1781cc66b1 Merge branch 'timers/nohz-ipi-for-tip-v3' of git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks into timers/nohz
> > 72aacf0259bb nohz: Move full nohz kick to its own IPI
> > 55d77c215c74 smp: Non busy-waiting IPI queue
> >
> > we can zap them all, or even keep 55d77c215c74.
> >
> > Frederic, which one would you prefer?
>
> I think we can zap them all. But since I'm not yet sure how the new
> solution, based on irq work, is going to be received, do you mind if
> we just wait for the new solution to be acked by Peterz?
>
> If that's ok for you, I'll then do a pull request that includes the
> solution and zaps the old two commits.

It's all isolated to timers/nohz, not mixed up with anything else, so
zapping it is easy (I already zapped the second commit) and you can
simply use latest -Linus to base your new solution on.

Thanks,

Ingo


\
 
 \ /
  Last update: 2014-05-11 08:21    [W:0.128 / U:0.288 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site