From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, cl@linux-foundation.org,
mingo@elte.hu, akpm@linux-foundation.org,
manfred@colorfullife.com, dipankar@in.ibm.com,
josht@linux.vnet.ibm.com, schamp@sgi.com, niv@us.ibm.com,
dvhltc@us.ibm.com, ego@in.ibm.com, laijs@cn.fujitsu.com,
rostedt@goodmis.org, peterz@infradead.org,
penberg@cs.helsinki.fi, tglx@linutronix.de
Subject: Re: [PATCH -tip] v9 scalable classic RCU implementation
Date: Tue, 2 Dec 2008 17:36:59 -0800 [thread overview]
Message-ID: <20081203013659.GH6719@linux.vnet.ibm.com> (raw)
In-Reply-To: <20081203011042.GH6703@one.firstfloor.org>
On Wed, Dec 03, 2008 at 02:10:42AM +0100, Andi Kleen wrote:
> > On Power, I see a hang in all three flavors of RCU when CPU hotplug
> > is enabled and dynticks is not. I have not yet seen this hang on x86.
> > On Power, the hang occurs in the CPU-offline code, and is identical to
> > the hangs I was seeing in 2.6.27, except that "sleep 1" does not hang
> > in recent 2.6.28 versions. So the timeout is apparently failing to fire
> > (or being ignored) for some other reason.
> >
> > Is this similar to what you are seeing on x86?
>
> Yes it is.
OK, then I will consider them to be the same bug for the moment.
Thanx, Paul
next prev parent reply other threads:[~2008-12-03 1:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 22:21 [PATCH -tip] v9 scalable classic RCU implementation Paul E. McKenney
2008-12-02 23:31 ` Andi Kleen
2008-12-02 23:51 ` Paul E. McKenney
2008-12-03 0:18 ` Andi Kleen
2008-12-03 0:47 ` Paul E. McKenney
2008-12-03 1:10 ` Andi Kleen
2008-12-03 1:36 ` Paul E. McKenney [this message]
2008-12-18 22:54 ` Paul E. McKenney
2008-12-19 1:29 ` Andi Kleen
2008-12-19 1:49 ` Paul E. McKenney
2008-12-03 8:40 ` Ingo Molnar
2008-12-17 0:37 ` [PATCH -tip] v10 " Paul E. McKenney
2008-12-17 2:03 ` Andrew Morton
2008-12-17 19:49 ` Paul E. McKenney
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=20081203013659.GH6719@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=ego@in.ibm.com \
--cc=josht@linux.vnet.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=schamp@sgi.com \
--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.