From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH RFC] KVM: MMU: Don't use RCU for lockless shadow walking Date: Tue, 24 Apr 2012 12:24:10 +0300 Message-ID: <4F96713A.9050706@redhat.com> References: <1335197812-32064-1-git-send-email-avi@redhat.com> <20120424011747.GA15748@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Xiao Guangrong , kvm@vger.kernel.org To: Marcelo Tosatti Return-path: Received: from mx1.redhat.com ([209.132.183.28]:53462 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755632Ab2DXJYO (ORCPT ); Tue, 24 Apr 2012 05:24:14 -0400 In-Reply-To: <20120424011747.GA15748@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: On 04/24/2012 04:17 AM, Marcelo Tosatti wrote: > On Mon, Apr 23, 2012 at 07:16:52PM +0300, Avi Kivity wrote: > > Using RCU for lockless shadow walking can increase the amount of memory > > in use by the system, since RCU grace periods are unpredictable. We also > > have an unconditional write to a shared variable (reader_counter), which > > isn't good for scaling. > > > > Replace that with a scheme similar to x86's get_user_pages_fast(): disable > > interrupts during lockless shadow walk to force the freer > > (kvm_mmu_commit_zap_page()) to wait for the TLB flush IPI to find the > > processor with interrupts enabled. > > > > We also add a new vcpu->mode, READING_SHADOW_PAGE_TABLES, to prevent > > kvm_flush_remote_tlbs() from avoiding the IPI. > > > > Should add an explicit mb after prepare_zap_page? (currently rely on > unrelated ones internal to flush_remote_tlbs). Yes. -- error compiling committee.c: too many arguments to function