linux-kernel - Re: [PATCH 0/4] rcu: Make new RCU dynticks API work with nohz cpusets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111129174448.GG2331@linux.vnet.ibm.com>
Date:	Tue, 29 Nov 2011 09:44:48 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Josh Triplett <josh@...htriplett.org>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] rcu: Make new RCU dynticks API work with nohz
 cpusets

On Tue, Nov 29, 2011 at 12:48:31AM -0800, Josh Triplett wrote:
> On Mon, Nov 28, 2011 at 09:43:42PM -0800, Paul E. McKenney wrote:
> > 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@...htriplett.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
> 
> Yes, for the ones with Frederic's further eagle-eyed fix.

Right, https://lkml.org/lkml/2011/11/28/626 above rather than my
erroneous https://lkml.org/lkml/2011/11/28/621.

Though I thought it was falcon-eyed rather than eagle-eyed.  ;-)

							Thanx, Paul

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/