From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754068Ab2KMIjx (ORCPT ); Tue, 13 Nov 2012 03:39:53 -0500 Received: from e28smtp09.in.ibm.com ([122.248.162.9]:33623 "EHLO e28smtp09.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751434Ab2KMIjw (ORCPT ); Tue, 13 Nov 2012 03:39:52 -0500 Message-ID: <50A20750.8050808@linux.vnet.ibm.com> Date: Tue, 13 Nov 2012 16:39:44 +0800 From: Xiao Guangrong User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: Marcelo Tosatti CC: Avi Kivity , LKML , KVM Subject: Re: [PATCH 2/5] KVM: MMU: simplify mmu_set_spte References: <5097AC70.1080904@linux.vnet.ibm.com> <5097ACA0.7080408@linux.vnet.ibm.com> <20121112231223.GC5798@amt.cnet> In-Reply-To: <20121112231223.GC5798@amt.cnet> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit x-cbid: 12111308-2674-0000-0000-000006B6F83D Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/13/2012 07:12 AM, Marcelo Tosatti wrote: > On Mon, Nov 05, 2012 at 08:10:08PM +0800, Xiao Guangrong wrote: >> In order to detecting spte remapping, we can simply check whether the >> spte has already been pointing to the pfn even if the spte is not the >> last spte for middle spte is pointing to the kernel pfn which can not >> be mapped to userspace >> >> Also, update slot and stat.lpages iff the spte is not remapped >> >> Signed-off-by: Xiao Guangrong >> --- >> arch/x86/kvm/mmu.c | 40 +++++++++++++--------------------------- >> 1 files changed, 13 insertions(+), 27 deletions(-) >> >> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c >> index 692ebb1..4ea731e 100644 >> --- a/arch/x86/kvm/mmu.c >> +++ b/arch/x86/kvm/mmu.c >> @@ -2420,8 +2420,7 @@ static void mmu_set_spte(struct kvm_vcpu *vcpu, u64 *sptep, >> pfn_t pfn, bool speculative, >> bool host_writable) >> { >> - int was_rmapped = 0; >> - int rmap_count; >> + bool was_rmapped = false; >> >> pgprintk("%s: spte %llx access %x write_fault %d" >> " user_fault %d gfn %llx\n", >> @@ -2429,25 +2428,13 @@ static void mmu_set_spte(struct kvm_vcpu *vcpu, u64 *sptep, >> write_fault, user_fault, gfn); >> >> if (is_rmap_spte(*sptep)) { >> - /* >> - * If we overwrite a PTE page pointer with a 2MB PMD, unlink >> - * the parent of the now unreachable PTE. >> - */ >> - if (level > PT_PAGE_TABLE_LEVEL && >> - !is_large_pte(*sptep)) { >> - struct kvm_mmu_page *child; >> - u64 pte = *sptep; >> + if (pfn != spte_to_pfn(*sptep)) { >> + struct kvm_mmu_page *sp = page_header(__pa(sptep)); >> >> - child = page_header(pte & PT64_BASE_ADDR_MASK); >> - drop_parent_pte(child, sptep); >> - kvm_flush_remote_tlbs(vcpu->kvm); > > How come its safe to drop this case? We use "if (pfn != spte_to_pfn(*sptep))" to simplify the thing. There are two cases: 1) the sptep is not the last mapping. under this case, sptep must point to a shadow page table, that means spte_to_pfn(*sptep)) is used by KVM module, and 'pfn' is used by userspace. so, 'if' condition must be satisfied, the sptep will be dropped. Actually, This is the origin case: | if (level > PT_PAGE_TABLE_LEVEL && | !is_large_pte(*sptep))" 2) the sptep is the last mapping. under this case, the level of spte (sp.level) must equal the 'level' which we pass to mmu_set_spte. If they point to the same pfn, it is 'remap', otherwise we drop it. I think this is safe. :)