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 <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] KVM: MMU: optimize pte write path if don't have protected sp
Date: Tue, 05 Apr 2011 11:34:43 +0300 [thread overview]
Message-ID: <4D9AD423.6060503@redhat.com> (raw)
In-Reply-To: <4D8FF2D2.9070109@cn.fujitsu.com>
On 03/28/2011 04:30 AM, Xiao Guangrong wrote:
> Simplely return from kvm_mmu_pte_write path if no shadow page is
> write-protected, than we can avoid to walk all shadow pages and hold
> mmu-lock
>
> Signed-off-by: Xiao Guangrong<xiaoguangrong@cn.fujitsu.com>
> ---
> arch/x86/kvm/mmu.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 2841805..ccac6c4 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -3219,6 +3219,11 @@ static void kvm_mmu_access_page(struct kvm_vcpu *vcpu, gfn_t gfn)
> set_bit(PT_ACCESSED_SHIFT, (unsigned long *)spte);
> }
>
> +static bool need_track_pte_changed(struct kvm_vcpu *vcpu)
> +{
> + return !tdp_enabled || mmu_is_nested(vcpu);
> +}
> +
What happens if this vcpu is nested but another vcpu is not?
Or if we have some indirect pages, but currently we're in non-nested mode?
Suggest instead to keep track of the number of indirect pages across the
guest. If it's zero, we can exit early.
> void kvm_mmu_pte_write(struct kvm_vcpu *vcpu, gpa_t gpa,
> const u8 *new, int bytes,
> bool guest_initiated)
> @@ -3233,6 +3238,9 @@ void kvm_mmu_pte_write(struct kvm_vcpu *vcpu, gpa_t gpa,
> int level, npte, invlpg_counter, r, flooded = 0;
> bool remote_flush, local_flush, zap_page;
>
> + if (!need_track_pte_changed(vcpu))
> + return;
> +
> zap_page = remote_flush = local_flush = false;
> offset = offset_in_page(gpa);
>
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-04-05 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 2:29 [PATCH 1/2] KVM: MMU: remove mmu_seq verification on pte write path Xiao Guangrong
2011-03-28 2:30 ` [PATCH 2/2] KVM: MMU: optimize pte write path if don't have protected sp Xiao Guangrong
2011-04-05 8:34 ` Avi Kivity [this message]
2011-04-05 8:35 ` [PATCH 1/2] KVM: MMU: remove mmu_seq verification on pte write path 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=4D9AD423.6060503@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