From mboxrd@z Thu Jan  1 00:00:00 1970
From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Subject: Re: [PATCH 1/2] KVM: MMU: allow more page become unsync at gfn mapping
 time
Date: Mon, 24 May 2010 10:03:52 +0800
Message-ID: <4BF9DE88.4060609@cn.fujitsu.com>
References: <4BF91C34.6020904@cn.fujitsu.com> <4BF932DD.5070900@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	KVM list <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <4BF932DD.5070900@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org



Avi Kivity wrote:

>> +    if (need_unsync)
>> +        kvm_unsync_pages(vcpu, gfn);
>>       return 0;
>>   }
>>
>>    
> 
> Looks good, I'm just uncertain about role.invalid handling.  What's the
> reasoning here?
>

Avi,

Thanks for your reply.

We no need worry about 'role.invalid' here, since we only allow the PTE shadow
pages(role.level == 1) become unsync, and in current code, 'role.invalid' is only
used for root shadow pages.