From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Greg KH <greg@kroah.com>,
Frank Blaschka <frank.blaschka@de.ibm.com>,
linux-kernel@vger.kernel.org, stable@kernel.org,
Christof Schmitt <christof.schmitt@de.ibm.com>,
Horst Hartmann <horsth@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [stable] [patch 2/3] nohz: fix printk_needs_cpu() return value on offline cpus
Date: Wed, 08 Dec 2010 12:13:30 +0100 [thread overview]
Message-ID: <1291806810.28378.2.camel@laptop> (raw)
In-Reply-To: <20101208080749.GB2523@osiris.boeblingen.de.ibm.com>
On Wed, 2010-12-08 at 09:07 +0100, Heiko Carstens wrote:
> On Tue, Dec 07, 2010 at 01:32:41PM -0800, Greg KH wrote:
> > On Fri, Nov 26, 2010 at 01:11:52PM +0100, Peter Zijlstra wrote:
> > > On Fri, 2010-11-26 at 13:00 +0100, Heiko Carstens wrote:
> > > > plain text document attachment (002_printk_needs_cpu.diff)
> > > > From: Heiko Carstens <heiko.carstens@de.ibm.com>
> > > >
> > > > This patch fixes a hang observed with 2.6.32 kernels where timers got
> > > > enqueued on offline cpus.
> [...]
> >
> > Is this going to make it into .37, or is it going to wait until .38?
>
> I hope it will go into .37. The same should be true for the
> get_next_timer_interrupt() which addresses the same problem.
> Peter, Ingo?
Ingo just send the pull request to Linus for two of the three patches,
I'll try and feed him the last one today.
next prev parent reply other threads:[~2010-12-08 11:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 12:00 [patch 0/3] three cpu hotplug fixes Heiko Carstens
2010-11-26 12:00 ` [patch 1/3] printk: fix wake_up_klogd() vs cpu hotplug Heiko Carstens
2010-11-26 12:10 ` Peter Zijlstra
2010-11-26 12:13 ` Heiko Carstens
2010-11-26 12:15 ` Peter Zijlstra
2010-11-26 12:35 ` Eric Dumazet
2010-11-26 12:42 ` Heiko Carstens
2010-11-26 13:01 ` Eric Dumazet
2010-11-26 15:02 ` [tip:sched/urgent] printk: Fix " tip-bot for Heiko Carstens
2010-11-26 12:00 ` [patch 2/3] nohz: fix printk_needs_cpu() return value on offline cpus Heiko Carstens
2010-11-26 12:11 ` Peter Zijlstra
2010-12-07 21:32 ` [stable] " Greg KH
2010-12-08 8:07 ` Heiko Carstens
2010-12-08 11:13 ` Peter Zijlstra [this message]
2010-11-26 15:02 ` [tip:sched/urgent] nohz: Fix " tip-bot for Heiko Carstens
2010-11-26 16:22 ` [PATCH] printk: use this_cpu_{read|write} api on printk_pending Eric Dumazet
2010-11-26 16:29 ` Peter Zijlstra
2010-11-26 16:40 ` Christoph Lameter
2010-11-26 16:59 ` Eric Dumazet
2010-11-26 17:11 ` Christoph Lameter
2010-11-26 17:20 ` Eric Dumazet
2010-11-26 17:27 ` Christoph Lameter
2010-12-08 20:41 ` [tip:sched/core] printk: Use " tip-bot for Eric Dumazet
2010-12-08 21:47 ` Christoph Lameter
2010-12-09 1:43 ` Eric Dumazet
2010-12-09 23:38 ` Christoph Lameter
2010-11-26 12:01 ` [patch 3/3] nohz/s390: fix arch_needs_cpu() return value on offline cpus Heiko Carstens
2010-11-26 12:14 ` Peter Zijlstra
2010-11-26 12:17 ` Heiko Carstens
2010-12-01 9:11 ` Heiko Carstens
2010-12-01 12:19 ` Peter Zijlstra
2010-12-08 20:41 ` [tip:sched/urgent] nohz: Fix get_next_timer_interrupt() vs cpu hotplug tip-bot for Heiko Carstens
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=1291806810.28378.2.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=christof.schmitt@de.ibm.com \
--cc=frank.blaschka@de.ibm.com \
--cc=greg@kroah.com \
--cc=heiko.carstens@de.ibm.com \
--cc=horsth@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schwidefsky@de.ibm.com \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.