From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755345Ab2BBQPu (ORCPT ); Thu, 2 Feb 2012 11:15:50 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48028 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752888Ab2BBQPt (ORCPT ); Thu, 2 Feb 2012 11:15:49 -0500 Message-ID: <4F2AB66C.2030309@redhat.com> Date: Thu, 02 Feb 2012 18:14:36 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: paulmck@linux.vnet.ibm.com CC: Christoph Lameter , Peter Zijlstra , Gilad Ben-Yossef , linux-kernel@vger.kernel.org, Chris Metcalf , Frederic Weisbecker , linux-mm@kvack.org, Pekka Enberg , Matt Mackall , Sasha Levin , Rik van Riel , Andi Kleen , Mel Gorman , Andrew Morton , Alexander Viro , Michal Nazarewicz , Kosaki Motohiro , Milton Miller Subject: Re: [v7 0/8] Reduce cross CPU IPI interference References: <1327572121-13673-1-git-send-email-gilad@benyossef.com> <1327591185.2446.102.camel@twins> <1328117722.2446.262.camel@twins> <20120201184045.GG2382@linux.vnet.ibm.com> <20120201201336.GI2382@linux.vnet.ibm.com> <4F2A58A1.90800@redhat.com> <20120202153437.GD2518@linux.vnet.ibm.com> In-Reply-To: <20120202153437.GD2518@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/02/2012 05:34 PM, Paul E. McKenney wrote: > On Thu, Feb 02, 2012 at 11:34:25AM +0200, Avi Kivity wrote: > > On 02/01/2012 10:13 PM, Paul E. McKenney wrote: > > > > > > > > Could we also apply the same approach to processors busy doing > > > > computational work? In that case the OS is also not needed. Interrupting > > > > these activities is impacting on performance and latency. > > > > > > Yep, that is in fact what Frederic's dyntick-idle userspace work does. > > > > Running in a guest is a special case of running in userspace, so we'd > > need to extend this work to kvm as well. > > As long as rcu_idle_enter() is called at the appropriate time, RCU will > happily ignore the CPU. ;-) > It's not called (since the cpu is not idle). Instead we call rcu_virt_note_context_switch(). -- error compiling committee.c: too many arguments to function