public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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/2] KVM: MMU: allow more page become unsync at getting sp time
Date: Mon, 24 May 2010 10:31:39 +0800	[thread overview]
Message-ID: <4BF9E50B.6010205@cn.fujitsu.com> (raw)
In-Reply-To: <4BF9378B.4080703@redhat.com>



Avi Kivity wrote:
> On 05/23/2010 03:16 PM, Xiao Guangrong wrote:
>> Allow more page become asynchronous at getting sp time, if need create
>> new
>> shadow page for gfn but it not allow unsync(level>  1), we should
>> unsync all
>> gfn's unsync page
>>
>>
>>
>> +/* @gfn should be write-protected at the call site */
>> +static void kvm_sync_pages(struct kvm_vcpu *vcpu,  gfn_t gfn)
>> +{
>> +    struct hlist_head *bucket;
>> +    struct kvm_mmu_page *s;
>> +    struct hlist_node *node, *n;
>> +    unsigned index;
>> +    bool flush = 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) {
>>    
> 
> role.direct, role.invalid?

We only handle unsync pages here, and 'role.direct' or 'role.invalid'
pages can't become unsync.

> 
> Well, role.direct cannot be unsync.  But that's not something we want to
> rely on.

While we mark the unsync page, we have filtered out the 'role.direct' pages,
so, i think we not need worry 'role.direct' here. :-)

> 
> This patch looks good too.
> 
> Some completely unrelated ideas:
> 
> - replace mmu_zap_page() calls in __kvm_sync_page() by setting
> role.invalid instead.  This reduces problems with the hash list being
> modified while we manipulate it.
> - add a for_each_shadow_page_direct() { ... } and
> for_each_shadow_page_indirect() { ... } to replace the
> hlist_for_each_entry_safe()s.

Actually, i have introduced for_each_gfn_sp() to cleanup it in my private
development. :-)

> - add kvm_tlb_gather() to reduce IPIs from kvm_mmu_zap_page()
> - clear spte.accessed on speculative sptes (for example from invlpg) so
> the swapper won't keep them in ram unnecessarily

I also noticed this problem

> 
> Again, completely unrelated to this patch set, just wrong them down so I
> don't forget them and to get your opinion.
> 

Your ideas are very valuable, and i'll do those if you are not free :-)

Thanks,
Xiao



  reply	other threads:[~2010-05-24  2:34 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 [this message]
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 ` [PATCH 1/2] KVM: MMU: allow more page become unsync at gfn mapping time Avi Kivity
2010-05-24  2:03   ` 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=4BF9E50B.6010205@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