From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/2] KVM: MMU: allow more page become unsync at gfn mapping time
Date: Sun, 23 May 2010 16:51:25 +0300 [thread overview]
Message-ID: <4BF932DD.5070900@redhat.com> (raw)
In-Reply-To: <4BF91C34.6020904@cn.fujitsu.com>
On 05/23/2010 03:14 PM, Xiao Guangrong wrote:
> In current code, shadow page can become asynchronous only if one
> shadow page for a gfn, this rule is too strict, in fact, we can
> let all last mapping page(i.e, it's the pte page) become unsync,
> and sync them at invlpg or flush tlb time.
>
> This patch allow more page become asynchronous at gfn mapping time
>
>
> +
> +static void kvm_unsync_pages(struct kvm_vcpu *vcpu, gfn_t gfn)
> {
> - unsigned index;
> struct hlist_head *bucket;
> struct kvm_mmu_page *s;
> struct hlist_node *node, *n;
> + unsigned index;
>
> - index = kvm_page_table_hashfn(sp->gfn);
> + index = kvm_page_table_hashfn(gfn);
> bucket =&vcpu->kvm->arch.mmu_page_hash[index];
> - /* don't unsync if pagetable is shadowed with multiple roles */
> +
> hlist_for_each_entry_safe(s, node, n, bucket, hash_link) {
> - if (s->gfn != sp->gfn || s->role.direct)
> + if (s->gfn != gfn || s->role.direct || s->unsync)
> continue;
>
role.invalid?
> - if (s->role.word != sp->role.word)
> - return 1;
> + WARN_ON(s->role.level != PT_PAGE_TABLE_LEVEL);
> + __kvm_unsync_page(vcpu, s);
> }
> - trace_kvm_mmu_unsync_page(sp);
> - ++vcpu->kvm->stat.mmu_unsync;
> - sp->unsync = 1;
> -
> - kvm_mmu_mark_parents_unsync(sp);
> -
> - mmu_convert_notrap(sp);
> - return 0;
> }
>
> static int mmu_need_write_protect(struct kvm_vcpu *vcpu, gfn_t gfn,
> bool can_unsync)
> {
> - struct kvm_mmu_page *shadow;
> + unsigned index;
> + struct hlist_head *bucket;
> + struct kvm_mmu_page *s;
> + struct hlist_node *node, *n;
> + bool need_unsync = false;
> +
> + index = kvm_page_table_hashfn(gfn);
> + bucket =&vcpu->kvm->arch.mmu_page_hash[index];
> + hlist_for_each_entry_safe(s, node, n, bucket, hash_link) {
> + if (s->gfn != gfn || s->role.direct)
> + continue;
>
> - shadow = kvm_mmu_lookup_page(vcpu->kvm, gfn);
> - if (shadow) {
> - if (shadow->role.level != PT_PAGE_TABLE_LEVEL)
> + if (s->role.level != PT_PAGE_TABLE_LEVEL)
> return 1;
>
role.invalid?
> - if (shadow->unsync)
> - return 0;
> - if (can_unsync&& oos_shadow)
> - return kvm_unsync_page(vcpu, shadow);
> - return 1;
> +
> + if (!need_unsync&& !s->unsync) {
> + if (!can_unsync || !oos_shadow)
> + return 1;
> + need_unsync = true;
> + }
> }
> + 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?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-05-23 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 12:14 [PATCH 1/2] KVM: MMU: allow more page become unsync at gfn mapping time Xiao Guangrong
2010-05-23 12:16 ` [PATCH 2/2] KVM: MMU: allow more page become unsync at getting sp time Xiao Guangrong
2010-05-23 14:11 ` Avi Kivity
2010-05-24 2:31 ` Xiao Guangrong
2010-05-24 6:25 ` Avi Kivity
2010-05-24 7:41 ` [PATCH 2/2 v2] " Xiao Guangrong
2010-05-25 9:32 ` Avi Kivity
2010-05-23 13:51 ` Avi Kivity [this message]
2010-05-24 2:03 ` [PATCH 1/2] KVM: MMU: allow more page become unsync at gfn mapping time Xiao Guangrong
2010-05-24 6:24 ` Avi Kivity
2010-05-24 7:14 ` Xiao Guangrong
2010-05-24 7:40 ` [PATCH 1/2 v2] " Xiao Guangrong
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=4BF932DD.5070900@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@cn.fujitsu.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).