From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: bharata@linux.vnet.ibm.com, Yong Zhang <yong.zhang0@gmail.com>,
linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH -tip 1/2] [PATCH -tip 1/2] sched: Reinstate group names in /proc/sched_debug.
Date: Wed, 12 Jan 2011 15:16:02 -0800 [thread overview]
Message-ID: <20110112231602.GH17328@linux.vnet.ibm.com> (raw)
In-Reply-To: <1294831112.19601.8.camel@laptop>
On Wed, Jan 12, 2011 at 12:18:32PM +0100, Peter Zijlstra wrote:
> On Wed, 2011-01-12 at 13:19 +0530, Bharata B Rao wrote:
> >
> > We could, but I guess its not a recommended practice anymore to depend on
> > spinlocks to protect rcu readside.
>
> Not only is it not recommended, its a flat out bug for PREEMPT_RCU.
And lockdep-RCU will yell at you under PREEMPT_RCU, which will result
in Miles Lane yelling at me. ;-)
Thanx, Paul
next prev parent reply other threads:[~2011-01-12 23:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 10:10 [PATCH -tip 0/2] sched: Get group names back in /proc/sched_debug - v1 Bharata B Rao
2011-01-11 10:11 ` [PATCH -tip 1/2] [PATCH -tip 1/2] sched: Reinstate group names in /proc/sched_debug Bharata B Rao
2011-01-11 12:46 ` Yong Zhang
2011-01-11 13:42 ` Bharata B Rao
2011-01-11 14:00 ` Yong Zhang
2011-01-12 7:49 ` Bharata B Rao
2011-01-12 9:17 ` Yong Zhang
2011-01-12 11:18 ` Peter Zijlstra
2011-01-12 23:16 ` Paul E. McKenney [this message]
2011-01-13 1:24 ` Yong Zhang
2011-01-18 19:04 ` [tip:sched/urgent] " tip-bot for Bharata B Rao
2011-01-11 10:12 ` [PATCH -tip 2/2] sched: Display autogroup " Bharata B Rao
2011-01-18 19:05 ` [tip:sched/urgent] " tip-bot for Bharata B Rao
2011-01-11 10:29 ` [PATCH -tip 0/2] sched: Get group names back in /proc/sched_debug - v1 Mike Galbraith
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=20110112231602.GH17328@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bharata@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yong.zhang0@gmail.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;
as well as URLs for NNTP newsgroup(s).