From: Andrew Morton <akpm@linux-foundation.org>
To: paulmck@linux.vnet.ibm.com
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
jarkao2@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] fix boot-time hangs from PREEMPT_RCU and NO_HZ
Date: Thu, 28 Feb 2008 21:01:40 -0800 [thread overview]
Message-ID: <20080228210140.37abe9cd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080229044329.GA20207@linux.vnet.ibm.com>
On Thu, 28 Feb 2008 20:43:29 -0800 "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> This is a repost of http://lkml.org/lkml/2008/2/2/11. It is needed in
> 2.6.25 in order to prevent boot-time hangs when running with PREEMPT_RCU
> and NO_HZ.
>
> Preemptible RCU can get stuck if a CPU goes idle and NO_HZ is set. The
> idle CPU will not progress the RCU through its grace period, so that
> any subsequent synchronize_rcu() invocations can hang until such time
> as a process starts running on the idle CPU. If no such process runs,
> subsequent synchronize_rcu() invocations will hang indefinitely, in turn
> hanging the system. Without this patch, one of Steve Rostedt's boxes
> hangs on boot when PREEMPT_RCU and NO_HZ are set. That same box boots
> fine with this patch.
>
> Note: This patch came directly from the -rt patch where it has been tested
> for several months.
>
> Andrew, could you please apply this?
I already have it, via git-sched. Presumably Ingo has it lined up for the
next sched-related merge.
next prev parent reply other threads:[~2008-02-29 5:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0801291113350.20371@gandalf.stny.rr.com>
2008-02-29 4:43 ` [PATCH] fix boot-time hangs from PREEMPT_RCU and NO_HZ Paul E. McKenney
2008-02-29 5:01 ` Andrew Morton [this message]
2008-02-29 15:48 ` Ingo Molnar
2008-02-29 16:55 ` Paul E. McKenney
2008-02-29 16:57 ` Ingo Molnar
2008-02-29 17:08 ` Steven Rostedt
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=20080228210140.37abe9cd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jarkao2@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).