From: Peter Zijlstra <peterz@infradead.org>
To: Cheng Xu <chengxu@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Paul Mckenney <paulmck@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH] sched: lockdep circular locking error (rcu_node_level_0 vs rq->lock)
Date: Thu, 21 Jul 2011 20:39:40 +0200 [thread overview]
Message-ID: <1311273580.29152.180.camel@twins> (raw)
In-Reply-To: <4E287177.6020605@linux.vnet.ibm.com>
On Fri, 2011-07-22 at 02:35 +0800, Cheng Xu wrote:
> This is an updated version of Peter Zijlstra's patch at
> https://lkml.org/lkml/2011/7/12/344 that successfully boots on IBM JS22
> Blade (with two Power6 quad-core CPUs). It might not be needed, but I am
> posting it just in case.
right, but if at all possible, I'd like to avoid actually doing this
since it adds more code to fairly hot paths. Furthermore it looks like
we sorted all issues in different ways.
But thanks!
prev parent reply other threads:[~2011-07-21 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 18:35 [RFC PATCH] sched: lockdep circular locking error (rcu_node_level_0 vs rq->lock) Cheng Xu
2011-07-21 18:39 ` Peter Zijlstra [this message]
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=1311273580.29152.180.camel@twins \
--to=peterz@infradead.org \
--cc=chengxu@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
/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