From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/5] KVM: MMU: split the operations of kvm_mmu_zap_page()
Date: Mon, 31 May 2010 10:13:49 +0800 [thread overview]
Message-ID: <4C031B5D.3000502@cn.fujitsu.com> (raw)
In-Reply-To: <4C026543.20608@redhat.com>
Avi Kivity wrote:
> On 05/30/2010 03:37 PM, Xiao Guangrong wrote:
>> Using kvm_mmu_prepare_zap_page() and kvm_mmu_commit_zap_page() to
>> split kvm_mmu_zap_page() function, then we can:
>>
>> - traverse hlist safely
>> - easily to gather remote tlb flush which occurs during page zapped
>>
>>
>> +static int kvm_mmu_prepare_zap_page(struct kvm *kvm, struct
>> kvm_mmu_page *sp)
>> +{
>> + int ret;
>> +
>> + trace_kvm_mmu_zap_page(sp);
>> + ++kvm->stat.mmu_shadow_zapped;
>> + ret = mmu_zap_unsync_children(kvm, sp);
>> + kvm_mmu_page_unlink_children(kvm, sp);
>> + kvm_mmu_unlink_parents(kvm, sp);
>> + if (!sp->role.invalid&& !sp->role.direct)
>> + unaccount_shadowed(kvm, sp->gfn);
>> + if (sp->unsync)
>> + kvm_unlink_unsync_page(kvm, sp);
>> + if (!sp->root_count)
>> + /* Count self */
>> + ret++;
>> + else
>> + kvm_reload_remote_mmus(kvm);
>> +
>> + sp->role.invalid = 1;
>> + list_move(&sp->link,&kvm->arch.invalid_mmu_pages);
>> + kvm_mmu_reset_last_pte_updated(kvm);
>> + return ret;
>> +}
>> +
>> +static void kvm_mmu_commit_zap_page(struct kvm *kvm)
>> +{
>> + struct kvm_mmu_page *sp, *n;
>> +
>> + if (list_empty(&kvm->arch.invalid_mmu_pages))
>> + return;
>> +
>> + kvm_flush_remote_tlbs(kvm);
>> + list_for_each_entry_safe(sp, n,&kvm->arch.invalid_mmu_pages, link) {
>> + WARN_ON(!sp->role.invalid);
>> + if (!sp->root_count)
>> + kvm_mmu_free_page(kvm, sp);
>> + }
>> +}
>> +
>>
>
> You're adding two new functions but not using them here? Possibly in
> the old kvm_mmu_zap_page()?
I use those in the next patch, it's not in kvm_mmu_zap_page(), it's used like:
hold mmu spin lock
kvm_mmu_prepare_zap_page page A
kvm_mmu_prepare_zap_page page B
kvm_mmu_prepare_zap_page page C
......
kvm_mmu_commit_zap_page
release mmu spin lock
>
>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>> index 5e5cd8d..225c3c4 100644
>> --- a/arch/x86/kvm/x86.c
>> +++ b/arch/x86/kvm/x86.c
>> @@ -5331,6 +5331,7 @@ struct kvm *kvm_arch_create_vm(void)
>> }
>>
>> INIT_LIST_HEAD(&kvm->arch.active_mmu_pages);
>> + INIT_LIST_HEAD(&kvm->arch.invalid_mmu_pages);
>> INIT_LIST_HEAD(&kvm->arch.assigned_dev_head);
>>
>
> This is a good idea, but belongs in a separate patch? We can use it to
> reclaim invalid pages before allocating new ones.
>
This patch is very simple and kvm_mmu_commit_zap_page() function should depend on
kvm->arch.invalid_mmu_pages, so i think we on need separate this patch, your opinion? :-)
Thanks,
Xiao
next prev parent reply other threads:[~2010-05-31 2:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 12:36 [PATCH 1/5] KVM: MMU: introduce some macros to cleanup hlist traverseing Xiao Guangrong
2010-05-30 12:37 ` [PATCH 2/5] KVM: MMU: split the operations of kvm_mmu_zap_page() Xiao Guangrong
2010-05-30 13:16 ` Avi Kivity
2010-05-31 2:13 ` Xiao Guangrong [this message]
2010-05-31 11:05 ` Avi Kivity
2010-06-01 2:29 ` Xiao Guangrong
2010-06-01 8:08 ` Avi Kivity
2010-05-30 12:39 ` [PATCH 3/5] KVM: MMU: gather remote tlb flush which occurs during page zapped Xiao Guangrong
2010-05-30 12:40 ` [PATCH 4/5] KVM: MMU: traverse sp hlish safely Xiao Guangrong
2010-05-30 12:42 ` [PATCH 5/5] KVM: MMU: reduce remote tlb flush in kvm_mmu_pte_write() Xiao Guangrong
2010-05-30 13:12 ` [PATCH 1/5] KVM: MMU: introduce some macros to cleanup hlist traverseing Avi Kivity
2010-05-31 2:00 ` Xiao Guangrong
2010-05-31 11:14 ` Avi Kivity
2010-06-01 2:38 ` Xiao Guangrong
2010-06-01 8:09 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C031B5D.3000502@cn.fujitsu.com \
--to=xiaoguangrong@cn.fujitsu.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).