From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] rcu: Make new RCU dynticks API work with nohz cpusets
Date: Mon, 28 Nov 2011 21:43:42 -0800 [thread overview]
Message-ID: <20111129054342.GA2375@linux.vnet.ibm.com> (raw)
In-Reply-To: <20111129052225.GB14546@leaf>
On Mon, Nov 28, 2011 at 09:22:25PM -0800, Josh Triplett wrote:
> On Mon, Nov 28, 2011 at 10:24:43PM +0100, Frederic Weisbecker wrote:
> > Hi Paul,
> >
> > This is an attempt to make the current RCU dynticks API
> > working with the nohz cpusets.
> >
> > I believe the two first patches could be pushed in your trees.
> > Patches 3 and 4 are rather something I plan to apply in mine,
> > given they are not needed upstream yet.
> >
> > Waiting for your comments.
> >
> > Thanks.
> >
> > Frederic Weisbecker (4):
> > rcu: Don't check irq nesting from rcu idle entry/exit
> > rcu: Irq nesting is always 0 on rcu_enter_idle_common
> > rcu: New rcu_user_enter() and rcu_user_exit() APIs
> > rcu: New rcu_user_enter_irq() and rcu_user_exit_irq() APIs
>
> For the whole series:
>
> Reviewed-by: Josh Triplett <josh@joshtriplett.org>
Thank you, Josh!
Does that cover the conflict-resolved versions of the first two?
o https://lkml.org/lkml/2011/11/28/626
o https://lkml.org/lkml/2011/11/28/624
Thanx, Paul
next prev parent reply other threads:[~2011-11-29 5:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 21:24 [PATCH 0/4] rcu: Make new RCU dynticks API work with nohz cpusets Frederic Weisbecker
2011-11-28 21:24 ` [PATCH 1/4] rcu: Don't check irq nesting from rcu idle entry/exit Frederic Weisbecker
2011-11-29 0:22 ` Paul E. McKenney
2011-11-29 0:26 ` Frederic Weisbecker
2011-11-29 0:39 ` Paul E. McKenney
2011-11-29 0:58 ` Frederic Weisbecker
2011-11-28 21:24 ` [PATCH 2/4] rcu: Irq nesting is always 0 on rcu_enter_idle_common Frederic Weisbecker
2011-11-29 0:29 ` Paul E. McKenney
2011-11-29 1:00 ` Frederic Weisbecker
2011-11-28 21:24 ` [PATCH 3/4 RFC] rcu: New rcu_user_enter() and rcu_user_exit() APIs Frederic Weisbecker
2011-11-28 21:24 ` [PATCH 4/4 RFC] rcu: New rcu_user_enter_irq() and rcu_user_exit_irq() APIs Frederic Weisbecker
2011-11-28 21:53 ` Josh Triplett
2011-11-29 1:00 ` Paul E. McKenney
2011-11-29 5:21 ` Josh Triplett
2011-11-29 14:05 ` Frederic Weisbecker
2011-11-29 18:23 ` Paul E. McKenney
2011-11-29 13:53 ` Frederic Weisbecker
2011-11-29 5:22 ` [PATCH 0/4] rcu: Make new RCU dynticks API work with nohz cpusets Josh Triplett
2011-11-29 5:43 ` Paul E. McKenney [this message]
2011-11-29 8:48 ` Josh Triplett
2011-11-29 17:44 ` Paul E. McKenney
2011-11-29 18:07 ` 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=20111129054342.GA2375@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.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 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.