public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] sched: Teach might_sleep() about preemptible RCU
Date: Thu, 17 Dec 2009 11:49:31 -0800	[thread overview]
Message-ID: <20091217194931.GA13619@linux.vnet.ibm.com> (raw)
In-Reply-To: <20091217084912.GB1901@elte.hu>

On Thu, Dec 17, 2009 at 09:49:12AM +0100, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> 
> > On Wed, Dec 16, 2009 at 08:23:57PM +0100, Frederic Weisbecker wrote:
> > > On Wed, Dec 16, 2009 at 08:21:05PM +0100, Frederic Weisbecker wrote:
> > > > From: tip-bot for Frederic Weisbecker <fweisbec@gmail.com>
> > > 
> > > Crap... I think I'm really becoming this cyborg...
> > > 
> > > > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> > > > Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > > 
> > > Although I've happily put Paul's Reviewed-by tag in this v2,
> > > I'd feel more comfortable if he could confirm it :)
> > 
> > Given that I missed the TINY_RCU problem, I am not sure how much my 
> > Reviewed-by tag is worth, but I have no problem attaching it to this updated 
> > patch.  ;-)
> 
> Reviewed-by is valuable in terms of you both acking the patch and expressing 
> that you thought it through and like it. It does not mean you have done a 
> mental kernel build test of all 2^3000 kernel .config variants and have proven 
> the patch correct under circumstances! :-)
> 
> So yes, i've added it - thanks Paul!

The one misgiving I have is that addition of threaded interrupts and
sleeping spinlocks might break this, but those changes will be large
enough that this is the least of the worries.  We might then need to
split might_sleep() into might_sleep() and might_sleep_rt(), but hard
to say before the fact.  And this check will be very worthwhile as-is
in the meantime!  ;-)

							Thanx, Paul

  reply	other threads:[~2009-12-17 19:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 22:44 [PATCH] sched: Teach might_sleep about preemptable rcu Frederic Weisbecker
2009-12-14 23:03 ` Paul E. McKenney
2009-12-16  8:18 ` [tip:sched/urgent] sched: Teach might_sleep() about preemptible RCU tip-bot for Frederic Weisbecker
2009-12-16 14:25   ` Ingo Molnar
2009-12-16 15:30     ` Paul E. McKenney
2009-12-16 18:57       ` Frederic Weisbecker
2009-12-16 19:13         ` Frederic Weisbecker
2009-12-16 19:21     ` [PATCH] " Frederic Weisbecker
2009-12-16 19:23       ` Frederic Weisbecker
2009-12-17  1:37         ` Paul E. McKenney
2009-12-17  8:49           ` Ingo Molnar
2009-12-17 19:49             ` Paul E. McKenney [this message]
2009-12-17 10:52       ` [tip:sched/urgent] " tip-bot for Frederic Weisbecker

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=20091217194931.GA13619@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    /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