From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 6/10] KVM: MMU: don not record gfn in kvm_mmu_pte_write Date: Sun, 06 Mar 2011 14:14:14 +0200 Message-ID: <4D737A96.6040409@redhat.com> References: <4D70C569.1030107@cn.fujitsu.com> <4D70C630.1080100@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , LKML , KVM To: Xiao Guangrong Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4960 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752738Ab1CFMOX (ORCPT ); Sun, 6 Mar 2011 07:14:23 -0500 In-Reply-To: <4D70C630.1080100@cn.fujitsu.com> Sender: kvm-owner@vger.kernel.org List-ID: On 03/04/2011 01:00 PM, Xiao Guangrong wrote: > No need to record the gfn to verifier the pte has the same mode as > current vcpu, it's because we only speculatively update the pte only > if the pte and vcpu have the same mode True. We can, as an additional cleanup, change mmu_pte_write_new_pte() to just do vcpu->arch.mmu.update_spte(...) instead of the if (). -- error compiling committee.c: too many arguments to function