Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756048AbZFEQ0N (ORCPT ); Fri, 5 Jun 2009 12:26:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752079AbZFEQZz (ORCPT ); Fri, 5 Jun 2009 12:25:55 -0400 Received: from e3.ny.us.ibm.com ([32.97.182.143]:45336 "EHLO e3.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751302AbZFEQZx (ORCPT ); Fri, 5 Jun 2009 12:25:53 -0400 Date: Fri, 5 Jun 2009 09:25:53 -0700 From: "Paul E. McKenney" To: Rusty Russell Cc: Gregory Haskins , "Michael S. Tsirkin" , Avi Kivity , Gregory Haskins , linux-kernel@vger.kernel.org, agraf@suse.de, pmullaney@novell.com, pmorreale@novell.com, anthony@codemonkey.ws, netdev@vger.kernel.org, kvm@vger.kernel.org, bhutchings@solarflare.com, andi@firstfloor.org, gregkh@suse.de, herber@gondor.apana.org.au, chrisw@sous-sol.org, shemminger@vyatta.com Subject: Re: [RFC PATCH v2 00/19] virtual-bus Message-ID: <20090605162553.GC6778@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20090409155200.32740.19358.stgit@dev.haskins.net> <200906051425.02924.rusty@rustcorp.com.au> <20090605053010.GD7125@linux.vnet.ibm.com> <200906060025.57961.rusty@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200906060025.57961.rusty@rustcorp.com.au> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2817 Lines: 85 On Sat, Jun 06, 2009 at 12:25:57AM +0930, Rusty Russell wrote: > On Fri, 5 Jun 2009 03:00:10 pm Paul E. McKenney wrote: > > On Fri, Jun 05, 2009 at 02:25:01PM +0930, Rusty Russell wrote: > > > + /* lg->eventfds is RCU-protected */ > > > + preempt_disable(); > > > > Suggest changing to rcu_read_lock() to match the synchronize_rcu(). > > Ah yes, much better. As I was implementing it I warred with myself since > lguest aims for simplicity above all else. But since we only ever add things > to the array, RCU probably is simpler. ;-) > > > + for (i = 0; i < cpu->lg->num_eventfds; i++) { > > > + if (cpu->lg->eventfds[i].addr == cpu->pending_notify) { > > > + eventfd_signal(cpu->lg->eventfds[i].event, 1); > > > > Shouldn't this be something like the following? > > > > p = rcu_dereference(cpu->lg->eventfds); > > if (p[i].addr == cpu->pending_notify) { > > eventfd_signal(p[i].event, 1); > > Hmm, need to read num_eventfds first, too. It doesn't matter if we get the old > ->num_eventfds and the new ->eventfds, but the other way around would be bad. Yep!!! ;-) > Here's the inter-diff: > > diff --git a/drivers/lguest/lguest_user.c b/drivers/lguest/lguest_user.c > --- a/drivers/lguest/lguest_user.c > +++ b/drivers/lguest/lguest_user.c > @@ -39,18 +39,24 @@ static int break_guest_out(struct lg_cpu > > bool send_notify_to_eventfd(struct lg_cpu *cpu) > { > - unsigned int i; > + unsigned int i, num; > + struct lg_eventfds *eventfds; > + > + /* Make sure we grab the total number before accessing the array. */ > + cpu->lg->num_eventfds = num; > + rmb(); > > /* lg->eventfds is RCU-protected */ > rcu_read_lock(); > - for (i = 0; i < cpu->lg->num_eventfds; i++) { > - if (cpu->lg->eventfds[i].addr == cpu->pending_notify) { > - eventfd_signal(cpu->lg->eventfds[i].event, 1); > + eventfds = rcu_dereference(cpu->lg->eventfds); > + for (i = 0; i < num; i++) { > + if (eventfds[i].addr == cpu->pending_notify) { > + eventfd_signal(eventfds[i].event, 1); > cpu->pending_notify = 0; > break; > } > } > - preempt_enable(); > + rcu_read_unlock(); > return cpu->pending_notify == 0; > } It is possible to get rid of the rmb() and wmb() as well, doing something like the following: struct lg_eventfds_num { unsigned int n; struct lg_eventfds a[0]; } Then the rcu_dereference() gets you a pointer to a struct lg_eventfds_num, which has the array and its length in guaranteed synchronization without the need for barriers. Does this work for you, or is there some complication that I am missing? Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/