Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758166Ab2EAPm2 (ORCPT ); Tue, 1 May 2012 11:42:28 -0400 Received: from merlin.infradead.org ([205.233.59.134]:35677 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756870Ab2EAPm0 convert rfc822-to-8bit (ORCPT ); Tue, 1 May 2012 11:42:26 -0400 Message-ID: <1335886921.13683.154.camel@twins> Subject: Re: [RFC PATCH v1 3/5] KVM: Add paravirt kvm_flush_tlb_others From: Peter Zijlstra To: Avi Kivity Cc: "Nikunj A. Dadhania" , mingo@elte.hu, jeremy@goop.org, mtosatti@redhat.com, kvm@vger.kernel.org, x86@kernel.org, vatsa@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, hpa@zytor.com Date: Tue, 01 May 2012 17:42:01 +0200 In-Reply-To: <4FA003C8.7060004@redhat.com> References: <20120427161727.27082.43096.stgit@abhimanyu> <20120427162401.27082.59387.stgit@abhimanyu> <4F9D32B4.8040002@redhat.com> <1335865176.13683.120.camel@twins> <4F9FBF38.2060903@redhat.com> <1335869827.13683.133.camel@twins> <4F9FD337.5010908@redhat.com> <1335884353.13683.144.camel@twins> <4FA001D8.6080801@redhat.com> <1335886587.13683.153.camel@twins> <4FA003C8.7060004@redhat.com> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 761 Lines: 18 On Tue, 2012-05-01 at 18:39 +0300, Avi Kivity wrote: > > rcu_read_{,un}lock_sched() -- aka preempt_{en,dis}able() > > call_rcu_sched() > > synchronize_rcu_sched() -- aka synchronize_sched(); > > > > Define an RCU variant where each cpu has to have scheduled at least once > > to complete a grace period. > > Which was the original rcu implementation, until it got replaced by > preemptible rcu, yes? I guess that was the source of my confusion. Indeed. The _sched RCU variant has the 'classic' RCU semantics. -- 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/