From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiao Guangrong Subject: Re: [PATCH v2 5/6] KVM: MMU: remove 'clear_unsync' parameter Date: Thu, 18 Nov 2010 15:42:01 +0800 Message-ID: <4CE4D8C9.90302@cn.fujitsu.com> References: <4CE355A0.6020907@cn.fujitsu.com> <4CE3565D.4080004@cn.fujitsu.com> <20101117164903.GE18959@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , LKML , KVM To: Marcelo Tosatti Return-path: In-Reply-To: <20101117164903.GE18959@amt.cnet> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 11/18/2010 12:49 AM, Marcelo Tosatti wrote: bool clear_unsync) >> +static int FNAME(sync_page)(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp) >> { >> int i, offset, nr_present; >> bool host_writable; >> @@ -781,7 +780,7 @@ static int FNAME(sync_page)(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, >> u64 nonpresent; >> >> if (rsvd_bits_set || is_present_gpte(gpte) || >> - !clear_unsync) >> + sp->unsync) >> nonpresent = shadow_trap_nonpresent_pte; >> else >> nonpresent = shadow_notrap_nonpresent_pte; > > Its better to keep this explicit as a parameter. > But after patch 6 (KVM: MMU: cleanup update_pte, pte_prefetch and sync_page functions), this parameter is not used anymore... i don't have strong opinion on it :-)