From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751837Ab1GTVkt (ORCPT ); Wed, 20 Jul 2011 17:40:49 -0400 Received: from e5.ny.us.ibm.com ([32.97.182.145]:55362 "EHLO e5.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750810Ab1GTVks (ORCPT ); Wed, 20 Jul 2011 17:40:48 -0400 Date: Wed, 20 Jul 2011 14:39:23 -0700 From: "Paul E. McKenney" To: Peter Zijlstra Cc: Linus Torvalds , Ingo Molnar , Ben Greear , Ed Tomlinson , linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com, akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca, josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de, rostedt@goodmis.org, Valdis.Kletnieks@vt.edu, dhowells@redhat.com, eric.dumazet@gmail.com, darren@dvhart.com, patches@linaro.org, edward.tomlinson@aero.bombardier.com Subject: Re: [PATCH rcu/urgent 0/6] Fixes for RCU/scheduler/irq-threads trainwreck Message-ID: <20110720213923.GT2313@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20110720044435.GB2400@linux.vnet.ibm.com> <20110720133443.GG2400@linux.vnet.ibm.com> <4E270A0E.6090902@candelatech.com> <20110720171532.GB2313@linux.vnet.ibm.com> <20110720184413.GD17977@elte.hu> <1311187978.29152.58.camel@twins> <20110720192949.GM2313@linux.vnet.ibm.com> <1311195953.29152.95.camel@twins> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1311195953.29152.95.camel@twins> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 20, 2011 at 11:05:53PM +0200, Peter Zijlstra wrote: > On Wed, 2011-07-20 at 12:29 -0700, Paul E. McKenney wrote: > > > Peter, does #4 (protect __rcu_read_unlock() against scheduler-using > > irq handlers) remove the need for #5 (Add irq_{enter,exit}() to > > scheduler_ipi()) and #6 (Inform RCU of irq_exit() activity)? My guess is > > "no" for #5 and "yes" for #6. > > More or less, we want to keep #5 for it does more than just fix RCU, but > yeah, I _think_ #4 obsoletes the direct need for #6. Heh. So the lowest risk is keeping #6 for now and deciding later whether we really need it. Thanx, Paul