From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, cl@linux-foundation.org,
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: Wed, 3 Dec 2008 09:40:13 +0100 [thread overview]
Message-ID: <20081203084013.GB5668@elte.hu> (raw)
In-Reply-To: <20081203004759.GG6719@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> I am currently undergoing a line-by-line code walkthrough of rcutree on
> the off-chance that all three versions of RCU suffer from the same bug.
> (And I have found a few bugs and spelling errors, but nothing related
> to the problem at hand.) If I don't find anything, I will start
> looking more closely at the CPU-hotplug code.
yep, CPU-hotplug is where i'd suspect problems, as it has changed
recently.
Ingo
next prev parent reply other threads:[~2008-12-03 8:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 22:21 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
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 [this message]
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=20081203084013.GB5668@elte.hu \
--to=mingo@elte.hu \
--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=niv@us.ibm.com \
--cc=paulmck@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®