Re: [GIT PULL] timers/nohz updates for v3.18

From: Greg KH
Date: Thu Oct 09 2014 - 09:51:15 EST


On Thu, Oct 09, 2014 at 02:57:25PM +0200, Frederic Weisbecker wrote:
> On Thu, Oct 09, 2014 at 06:34:26AM -0400, Linus Torvalds wrote:
> > Hmm..
> >
> > On Thu, Oct 9, 2014 at 2:48 AM, Ingo Molnar <mingo@xxxxxxxxxx> wrote:
> > >
> > > Please pull the latest timers-nohz-for-linus git tree from:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-nohz-for-linus
> > >
> > > # HEAD: 9b01f5bf3999a3db5b1bbd9fdfd80d8d304e94ee nohz: nohz full depends on irq work self IPI support
> > >
> > > Main changes:
> > >
> > > - Fix the deadlock reported by Dave Jones et al
> > > - Clean up and fix nohz_full interaction with arch abilities
> > > - nohz init code consolidation/cleanup
> >
> > Ok, pulled. But none of these are marked for stable, yet the deadlock
> > people are seeing is in 3.17. Is there a separate line of minimal
> > fixes just for that? Or was the lack of stable tags just an oversight?
>
> It was first intended because the patchset is quite invasive and nohz full has
> no known users, or perhaps there is one... So I thought that backporting
> could be more dangerous than anything.
>
> Now thinking more about it I could isolate the following patches for
> stable:
>
> irq_work: Introduce arch_irq_work_has_interrupt()
> irq_work: Force raised irq work to run on irq work interrupt
> x86: Tell irq work about self IPI support
> arm: Tell irq work about self IPI support
>
> Sending these to stable@xxxxxxxxxxxxxxx would catch up, right? I
> can still do that.

If I can just pick those patches directly, that's all I need for the
stable trees. What are the git ids in Linus's tree for these patches,
so that I know I got this correct?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/