From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752135Ab2GIRpr (ORCPT ); Mon, 9 Jul 2012 13:45:47 -0400 Received: from mail-yw0-f46.google.com ([209.85.213.46]:55498 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751604Ab2GIRpp (ORCPT ); Mon, 9 Jul 2012 13:45:45 -0400 Date: Mon, 9 Jul 2012 19:45:38 +0200 From: Frederic Weisbecker To: Avi Kivity Cc: "Paul E. McKenney" , LKML , Alessio Igor Bogani , Andrew Morton , Chris Metcalf , Christoph Lameter , Geoff Levand , Gilad Ben Yossef , Hakan Akkan , "H. Peter Anvin" , Ingo Molnar , Josh Triplett , Kevin Hilman , Max Krasnyansky , Peter Zijlstra , Stephen Hemminger , Steven Rostedt , Sven-Thorsten Dietrich , Thomas Gleixner , Marcelo Tosatti , KVM list Subject: Re: [PATCH 2/6] rcu: Allow rcu_user_enter()/exit() to nest Message-ID: <20120709174535.GD8185@somewhere.redhat.com> References: <1341576018-10721-1-git-send-email-fweisbec@gmail.com> <1341576018-10721-3-git-send-email-fweisbec@gmail.com> <4FF9AD2A.1000901@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FF9AD2A.1000901@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jul 08, 2012 at 06:54:18PM +0300, Avi Kivity wrote: > On 07/06/2012 03:00 PM, Frederic Weisbecker wrote: > > Allow calls to rcu_user_enter() even if we are already > > in userspace (as seen by RCU) and allow calls to rcu_user_exit() > > even if we are already in the kernel. > > > > This makes the APIs more flexible to be called from architectures. > > Exception entries for example won't need to know if they come from > > userspace before calling rcu_user_exit(). > > I guess I should switch kvm to rcu_user_enter() and co, so we can > disable the tick while running in a guest. But where are those > functions? What are the rules for calling them? I guess we need to have a closer look at the guest case first. We probably need to take some care about specifics in time and load accounting usually handled by the tick before we can shut it down. RCU is only part of the problem.