From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932976Ab2BBRwP (ORCPT ); Thu, 2 Feb 2012 12:52:15 -0500 Received: from e9.ny.us.ibm.com ([32.97.182.139]:45609 "EHLO e9.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757078Ab2BBRwJ (ORCPT ); Thu, 2 Feb 2012 12:52:09 -0500 Date: Thu, 2 Feb 2012 09:51:55 -0800 From: "Paul E. McKenney" To: Avi Kivity 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 Message-ID: <20120202175155.GV2518@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <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> <4F2AB66C.2030309@redhat.com> <20120202170134.GM2518@linux.vnet.ibm.com> <4F2AC69B.7000704@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F2AC69B.7000704@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Content-Scanned: Fidelis XPS MAILER x-cbid: 12020217-7182-0000-0000-000000A767C3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 02, 2012 at 07:23:39PM +0200, Avi Kivity wrote: > On 02/02/2012 07:01 PM, Paul E. McKenney wrote: > > > > > > It's not called (since the cpu is not idle). Instead we call > > > rcu_virt_note_context_switch(). > > > > Frederic's work checks to see if there is only one runnable user task > > on a given CPU. If there is only one, then the scheduling-clock interrupt > > is turned off for that CPU, and RCU is told to ignore it while it is > > executing in user space. Not sure whether this covers KVM guests. > > Conceptually it's the same. Maybe it needs adjustments, since kvm > enters a guest in a different way than the kernel exits to userspace. > > > In any case, this is not yet in mainline. > > Let me know when it's in, and I'll have a look. Could you please touch base with Frederic Weisbecker to make sure that what he is doing works for you? Thanx, Paul