All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: paulmck@linux.vnet.ibm.com
Cc: "Nikunj A. Dadhania" <nikunj@linux.vnet.ibm.com>,
	mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: remove rcu_read_lock from wake_affine
Date: Tue, 07 Jun 2011 19:29:23 +0200	[thread overview]
Message-ID: <1307467763.2322.282.camel@twins> (raw)
In-Reply-To: <20110607172606.GA2286@linux.vnet.ibm.com>

On Tue, 2011-06-07 at 10:26 -0700, Paul E. McKenney wrote:
> 
> Nikunj, one such approach is is "WARN_ON_ONCE(!rcu_read_lock_held())".
> 
> This will complain if this function is called without an rcu_read_lock()
> in effect, but only if CONFIG_PROVE_RCU=y.

rcu_lockdep_assert(rcu_read_lock_held()) would be nicer, however, since
the below:

> > >  static int wake_affine(struct sched_domain *sd, struct task_struct *p, int sync)
> > >  {
> > >     s64 this_load, load;
> > > @@ -1481,7 +1482,6 @@ static int wake_affine(struct sched_domain *sd, struct task_struct *p, int sync)
> > >      * effect of the currently running task from the load
> > >      * of the current CPU:
> > >      */
> > > -   rcu_read_lock();
> > >     if (sync) {
> > >             tg = task_group(current);
> > >             weight = current->se.load.weight; 

task_group() has an rcu_dereference_check() in, its really not needed,
the thing will yell if we get this wrong.

  reply	other threads:[~2011-06-07 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 10:13 [PATCH] sched: remove rcu_read_lock from wake_affine Nikunj A. Dadhania
2011-06-07 10:26 ` Peter Zijlstra
2011-06-07 17:26   ` Paul E. McKenney
2011-06-07 17:29     ` Peter Zijlstra [this message]
2011-06-07 18:11       ` Paul E. McKenney
2011-07-01 15:16 ` [tip:sched/core] sched: Remove rcu_read_lock() from wake_affine() tip-bot for Nikunj A. Dadhania

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=1307467763.2322.282.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nikunj@linux.vnet.ibm.com \
    --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 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.