From: Frederic Weisbecker <fweisbec@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>, stable <stable@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] timers/nohz updates for v3.18
Date: Thu, 9 Oct 2014 14:57:25 +0200 [thread overview]
Message-ID: <20141009125721.GA25790@lerouge> (raw)
In-Reply-To: <CA+55aFy5RDVOy79J-XkKVgpZhh8ph42pPeSFtFmWjFhyx-G8Yw@mail.gmail.com>
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@kernel.org> 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@vger.kernel.org would catch up, right? I
can still do that.
Thanks.
next prev parent reply other threads:[~2014-10-09 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 6:48 [GIT PULL] timers/nohz updates for v3.18 Ingo Molnar
2014-10-09 10:34 ` Linus Torvalds
2014-10-09 12:57 ` Frederic Weisbecker [this message]
2014-10-09 13:50 ` Greg KH
2014-10-09 14:36 ` Frederic Weisbecker
2014-10-09 15:14 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141009125721.GA25790@lerouge \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox