From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: avi@redhat.com, mtosatti@redhat.com
Cc: kvm@vger.kernel.org, yoshikawa.takuya@oss.ntt.co.jp
Subject: [RFC PATCH 3/3] KVM: MMU: Optimize guest page table walk
Date: Tue, 19 Apr 2011 03:38:14 +0900 [thread overview]
Message-ID: <20110419033814.3cc7ab5e.takuya.yoshikawa@gmail.com> (raw)
In-Reply-To: <20110419033220.e527bcae.takuya.yoshikawa@gmail.com>
From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
We optimize multi level guest page table walk as follows:
1. We cache the memslot which, probably, includes the next guest page
tables to avoid searching for it many times.
2. We use get_user() instead of copy_from_user().
Note that this is kind of a restricted way of Xiao's more generic
work: "KVM: optimize memslots searching and cache GPN to GFN."
With this patch applied, paging64_walk_addr_generic() has improved
as the following tracing results show.
Before:
3.169 us | paging64_walk_addr_generic();
1.880 us | paging64_walk_addr_generic();
1.243 us | paging64_walk_addr_generic();
1.517 us | paging64_walk_addr_generic();
3.009 us | paging64_walk_addr_generic();
1.814 us | paging64_walk_addr_generic();
1.340 us | paging64_walk_addr_generic();
1.659 us | paging64_walk_addr_generic();
1.748 us | paging64_walk_addr_generic();
1.488 us | paging64_walk_addr_generic();
After:
1.714 us | paging64_walk_addr_generic();
0.806 us | paging64_walk_addr_generic();
0.664 us | paging64_walk_addr_generic();
0.619 us | paging64_walk_addr_generic();
0.645 us | paging64_walk_addr_generic();
0.605 us | paging64_walk_addr_generic();
1.388 us | paging64_walk_addr_generic();
0.753 us | paging64_walk_addr_generic();
0.594 us | paging64_walk_addr_generic();
0.833 us | paging64_walk_addr_generic();
Signed-off-by: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
---
arch/x86/kvm/paging_tmpl.h | 37 ++++++++++++++++++++++++++++++++-----
1 files changed, 32 insertions(+), 5 deletions(-)
diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
index 109939a..614aa3f 100644
--- a/arch/x86/kvm/paging_tmpl.h
+++ b/arch/x86/kvm/paging_tmpl.h
@@ -109,12 +109,37 @@ static unsigned FNAME(gpte_access)(struct kvm_vcpu *vcpu, pt_element_t gpte)
return access;
}
+/*
+ * Read the guest PTE refered to by table_gfn and offset and put it into ptep.
+ *
+ * *slot_hint, if not NULL, should point to a memslot which probably includes
+ * the guest PTE. The actual memslot will be put back into this so that
+ * callers can cache it.
+ */
static int FNAME(read_guest_pte)(struct kvm_vcpu *vcpu, struct kvm_mmu *mmu,
- gfn_t table_gfn, int offset, pt_element_t *ptep)
+ gfn_t table_gfn, int offset, pt_element_t *ptep,
+ struct kvm_memory_slot **slot_hint)
{
- return kvm_read_guest_page_mmu(vcpu, mmu, table_gfn, ptep,
- offset, sizeof(*ptep),
- PFERR_USER_MASK | PFERR_WRITE_MASK);
+ unsigned long addr;
+ pt_element_t __user *ptep_user;
+ gfn_t real_gfn;
+
+ real_gfn = mmu->translate_gpa(vcpu, gfn_to_gpa(table_gfn),
+ PFERR_USER_MASK | PFERR_WRITE_MASK);
+ if (real_gfn == UNMAPPED_GVA)
+ return -EFAULT;
+
+ real_gfn = gpa_to_gfn(real_gfn);
+
+ if (!(*slot_hint) || !gfn_in_memslot(*slot_hint, real_gfn))
+ *slot_hint = gfn_to_memslot(vcpu->kvm, real_gfn);
+
+ addr = gfn_to_hva_memslot(*slot_hint, real_gfn);
+ if (kvm_is_error_hva(addr))
+ return -EFAULT;
+
+ ptep_user = (pt_element_t __user *)((void *)addr + offset);
+ return get_user(*ptep, ptep_user);
}
/*
@@ -130,6 +155,7 @@ static int FNAME(walk_addr_generic)(struct guest_walker *walker,
gpa_t pte_gpa;
bool eperm, present, rsvd_fault;
int offset, write_fault, user_fault, fetch_fault;
+ struct kvm_memory_slot *slot_cache = NULL;
write_fault = access & PFERR_WRITE_MASK;
user_fault = access & PFERR_USER_MASK;
@@ -168,7 +194,8 @@ walk:
walker->table_gfn[walker->level - 1] = table_gfn;
walker->pte_gpa[walker->level - 1] = pte_gpa;
- if (FNAME(read_guest_pte)(vcpu, mmu, table_gfn, offset, &pte)) {
+ if (FNAME(read_guest_pte)(vcpu, mmu, table_gfn,
+ offset, &pte, &slot_cache)) {
present = false;
break;
}
--
1.7.1
next prev parent reply other threads:[~2011-04-18 18:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 18:32 [PATCH 1/3] KVM: Introduce a helper to check if gfn is in memslot Takuya Yoshikawa
2011-04-18 18:34 ` [PATCH 2/3] KVM: MMU: Introduce a helper to read guest pte Takuya Yoshikawa
2011-04-20 9:07 ` Avi Kivity
2011-04-20 9:35 ` Roedel, Joerg
2011-04-20 10:05 ` Avi Kivity
2011-04-20 11:06 ` Roedel, Joerg
2011-04-20 11:18 ` Avi Kivity
2011-04-20 13:33 ` [PATCH] KVM: MMU: Make cmpxchg_gpte aware of nesting too Roedel, Joerg
2011-04-21 1:02 ` Takuya Yoshikawa
2011-04-21 8:11 ` Avi Kivity
2011-04-21 1:07 ` [PATCH 2/3] KVM: MMU: Introduce a helper to read guest pte Takuya Yoshikawa
2011-04-18 18:38 ` Takuya Yoshikawa [this message]
2011-04-18 18:52 ` [RFC PATCH 3/3] KVM: MMU: Optimize guest page table walk Joerg Roedel
2011-04-19 1:24 ` Takuya Yoshikawa
2011-04-19 6:20 ` Joerg Roedel
2011-04-19 1:42 ` Xiao Guangrong
2011-04-19 3:47 ` Takuya Yoshikawa
2011-04-20 9:09 ` Avi Kivity
2011-04-20 9:02 ` Avi Kivity
2011-04-29 2:46 ` Andi Kleen
2011-04-29 5:38 ` Takuya Yoshikawa
2011-04-29 6:30 ` Takuya Yoshikawa
2011-04-29 6:59 ` Andi Kleen
2011-04-29 13:51 ` Takuya Yoshikawa
2011-04-29 16:05 ` Andi Kleen
2011-05-01 13:32 ` Avi Kivity
2011-05-01 20:51 ` Andi Kleen
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=20110419033814.3cc7ab5e.takuya.yoshikawa@gmail.com \
--to=takuya.yoshikawa@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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).