From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756839Ab2K0Xm5 (ORCPT ); Tue, 27 Nov 2012 18:42:57 -0500 Received: from mx1.redhat.com ([209.132.183.28]:28405 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756017Ab2K0Xmy (ORCPT ); Tue, 27 Nov 2012 18:42:54 -0500 Date: Tue, 27 Nov 2012 21:42:03 -0200 From: Marcelo Tosatti To: Xiao Guangrong Cc: Avi Kivity , LKML , KVM Subject: Re: [PATCH 3/3] KVM: x86: improve reexecute_instruction Message-ID: <20121127234203.GC8295@amt.cnet> References: <50AAC77C.8040505@linux.vnet.ibm.com> <50AAC7F9.7050305@linux.vnet.ibm.com> <20121126224105.GB10634@amt.cnet> <50B433D0.8060107@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50B433D0.8060107@linux.vnet.ibm.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 Tue, Nov 27, 2012 at 11:30:24AM +0800, Xiao Guangrong wrote: > On 11/27/2012 06:41 AM, Marcelo Tosatti wrote: > > >> > >> - return false; > >> +again: > >> + page_fault_count = ACCESS_ONCE(vcpu->kvm->arch.page_fault_count); > >> + > >> + /* > >> + * if emulation was due to access to shadowed page table > >> + * and it failed try to unshadow page and re-enter the > >> + * guest to let CPU execute the instruction. > >> + */ > >> + kvm_mmu_unprotect_page(vcpu->kvm, gpa_to_gfn(gpa)); > >> + emulate = vcpu->arch.mmu.page_fault(vcpu, cr3, PFERR_WRITE_MASK, false); > > > > Can you explain what is the objective here? > > > > Sure. :) > > The instruction emulation is caused by fault access on cr3. After unprotect > the target page, we call vcpu->arch.mmu.page_fault to fix the mapping of cr3. > if it return 1, mmu can not fix the mapping, we should report the error, > otherwise it is good to return to guest and let it re-execute the instruction > again. > > page_fault_count is used to avoid the race on other vcpus, since after we > unprotect the target page, other cpu can enter page fault path and let the > page be write-protected again. > > This way can help us to detect all the case that mmu can not be fixed. How about recording the gfn number for shadow pages that have been shadowed in the current pagefault run? (which is cheap, compared to shadowing these pages). If failed instruction emulation is write to one of these gfns, then fail.