From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>,
kvm@vger.kernel.org, yoshikawa.takuya@oss.ntt.co.jp
Subject: Re: [PATCH 1/1 v2] KVM: MMU: Use ptep_user for cmpxchg_gpte()
Date: Wed, 04 May 2011 14:44:47 +0300 [thread overview]
Message-ID: <4DC13C2F.4090402@redhat.com> (raw)
In-Reply-To: <20110504111611.GA26538@amt.cnet>
On 05/04/2011 02:16 PM, Marcelo Tosatti wrote:
> On Sun, May 01, 2011 at 02:33:07PM +0900, Takuya Yoshikawa wrote:
> > From: Takuya Yoshikawa<yoshikawa.takuya@oss.ntt.co.jp>
> >
> > The address of the gpte was already calculated and stored in ptep_user
> > before entering cmpxchg_gpte().
> >
> > This patch makes cmpxchg_gpte() to use that to make it clear that we
> > are using the same address during walk_addr_generic().
> >
> > Note that the unlikely annotations are used to show that the conditions
> > are something unusual rather than for performance.
> >
> > Signed-off-by: Takuya Yoshikawa<yoshikawa.takuya@oss.ntt.co.jp>
> > ---
> > arch/x86/kvm/paging_tmpl.h | 26 ++++++++++++--------------
> > 1 files changed, 12 insertions(+), 14 deletions(-)
>
> Hi Takuya,
>
> >
> > diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
> > index 52450a6..f9d9af1 100644
> > --- a/arch/x86/kvm/paging_tmpl.h
> > +++ b/arch/x86/kvm/paging_tmpl.h
> > @@ -79,21 +79,19 @@ static gfn_t gpte_to_gfn_lvl(pt_element_t gpte, int lvl)
> > }
> >
> > static int FNAME(cmpxchg_gpte)(struct kvm_vcpu *vcpu, struct kvm_mmu *mmu,
> > - gfn_t table_gfn, unsigned index,
> > - pt_element_t orig_pte, pt_element_t new_pte)
> > + pt_element_t __user *ptep_user, unsigned index,
> > + pt_element_t orig_pte, pt_element_t new_pte)
> > {
> > + int npages;
> > pt_element_t ret;
> > pt_element_t *table;
> > struct page *page;
> > - gpa_t gpa;
> >
> > - gpa = mmu->translate_gpa(vcpu, table_gfn<< PAGE_SHIFT,
> > - PFERR_USER_MASK|PFERR_WRITE_MASK);
> > - if (gpa == UNMAPPED_GVA)
> > + npages = get_user_pages_fast((unsigned long)ptep_user, 1, 1,&page);
> > + /* Check if the user is doing something meaningless. */
> > + if (unlikely(npages != 1))
> > return -EFAULT;
> >
> > - page = gfn_to_page(vcpu->kvm, gpa_to_gfn(gpa));
> > -
>
> gfn_to_page is the interface for mapping guest pages inside KVM,
> and you're bypassing it for IMO no good reason (i doubt there's any
> performance improvement by skipping the translation).
He isn't skipping it - he's using gfn_to_hva() to derive ptep_user,
which is equivalent.
The motivation isn't performance, it's to ensure that cmpxchg_gpte()
operates on the same address as we read it from.
(btw, we're missing a mark_page_dirty() here, no?)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-04 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 5:30 [PATCH 0/1 v2] KVM: MMU: Use ptep_user for cmpxchg_gpte() Takuya Yoshikawa
2011-05-01 5:33 ` [PATCH 1/1 " Takuya Yoshikawa
2011-05-04 11:16 ` Marcelo Tosatti
2011-05-04 11:44 ` Avi Kivity [this message]
2011-05-04 11:58 ` Marcelo Tosatti
2011-05-04 12:11 ` Avi Kivity
2011-05-04 14:00 ` Takuya Yoshikawa
2011-05-04 14:27 ` Avi Kivity
2011-05-04 16:13 ` Marcelo Tosatti
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=4DC13C2F.4090402@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=takuya.yoshikawa@gmail.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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).