From: Marcelo Tosatti <mtosatti@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Avi Kivity <avi@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH v6 3/3] KVM: MMU: prefetch ptes when intercepted guest #PF
Date: Mon, 16 Aug 2010 12:43:44 -0300 [thread overview]
Message-ID: <20100816154343.GA10363@amt.cnet> (raw)
In-Reply-To: <4C689653.2000400@cn.fujitsu.com>
On Mon, Aug 16, 2010 at 09:37:23AM +0800, Xiao Guangrong wrote:
> Hi Marcelo,
>
> Thanks for your review and sorry for the delay reply.
>
> Marcelo Tosatti wrote:
>
> >> +static struct kvm_memory_slot *
> >> +pte_prefetch_gfn_to_memslot(struct kvm_vcpu *vcpu, gfn_t gfn, bool no_dirty_log)
> >> +{
> >> + struct kvm_memory_slot *slot;
> >> +
> >> + slot = gfn_to_memslot(vcpu->kvm, gfn);
> >> + if (!slot || slot->flags & KVM_MEMSLOT_INVALID ||
> >> + (no_dirty_log && slot->dirty_bitmap))
> >> + slot = NULL;
> >
> > Why is this no_dirty_log optimization worthwhile?
> >
>
> We disable prefetch the writable pages since 'pte prefetch' will hurt slot's
> dirty page tracking that it set the dirty_bitmap bit but the corresponding page
> is not really accessed.
>
> >> +
> >> + return slot;
> >> +}
> >> +
> >> +static pfn_t pte_prefetch_gfn_to_pfn(struct kvm_vcpu *vcpu, gfn_t gfn,
> >> + bool no_dirty_log)
> >> +{
> >> + struct kvm_memory_slot *slot;
> >> + unsigned long hva;
> >> +
> >> + slot = pte_prefetch_gfn_to_memslot(vcpu, gfn, no_dirty_log);
> >> + if (!slot) {
> >> + get_page(bad_page);
> >> + return page_to_pfn(bad_page);
> >> + }
> >> +
> >> + hva = gfn_to_hva_memslot(slot, gfn);
> >> +
> >> + return hva_to_pfn_atomic(vcpu->kvm, hva);
> >> +}
> >> +
> >> +static int direct_pte_prefetch_many(struct kvm_vcpu *vcpu,
> >> + struct kvm_mmu_page *sp,
> >> + u64 *start, u64 *end)
> >> +{
> >> + struct page *pages[PTE_PREFETCH_NUM];
> >> + struct kvm_memory_slot *slot;
> >> + unsigned hva, access = sp->role.access;
> >> + int i, ret, npages = end - start;
> >> + gfn_t gfn;
> >> +
> >> + gfn = kvm_mmu_page_get_gfn(sp, start - sp->spt);
> >> + slot = pte_prefetch_gfn_to_memslot(vcpu, gfn, access & ACC_WRITE_MASK);
> >> + if (!slot || slot->npages - (gfn - slot->base_gfn) != npages)
> >> + return -1;
> >> +
> >> + hva = gfn_to_hva_memslot(slot, gfn);
> >> + ret = __get_user_pages_fast(hva, npages, 1, pages);
> >> + if (ret <= 0)
> >> + return -1;
> >
> > Better do one at a time with hva_to_pfn_atomic. Or, if you measure that
> > its worthwhile, do on a separate patch (using a helper as discussed
> > previously).
> >
>
> Since it should disable 'prefetch' for the writable pages, so i'm not put these
> operations into a common function and define it in kvm_main.c file.
>
> Maybe we do better do these in a wrap function named pte_prefetch_gfn_to_pages()?
Yes, please have it as a common function in kvm_main.c.
prev parent reply other threads:[~2010-08-16 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 3:28 [PATCH v6 1/3] export __get_user_pages_fast() function Xiao Guangrong
2010-08-04 3:31 ` [PATCH v6 2/3] KVM: MMU: introduce hva_to_pfn_atomic function Xiao Guangrong
2010-08-04 3:33 ` [PATCH v6 3/3] KVM: MMU: prefetch ptes when intercepted guest #PF Xiao Guangrong
2010-08-05 14:38 ` Marcelo Tosatti
2010-08-16 1:37 ` Xiao Guangrong
2010-08-16 15:43 ` Marcelo Tosatti [this message]
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=20100816154343.GA10363@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).