From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: [PATCH 0/2] Keep cr3 cached in VMCS
Date: Sun, 5 Dec 2010 19:01:55 +0200 [thread overview]
Message-ID: <1291568517-8717-1-git-send-email-avi@redhat.com> (raw)
This patchset keeps cr3 cached in the VMCS (GUEST_CR3) instead of syncing
it every exit. Saves a VMEXIT on Intel with EPT enabled.
Avi Kivity (2):
KVM: Replace reads of vcpu->arch.cr3 by an accessor
KVM: Fetch guest cr3 from hardware on demand
arch/x86/include/asm/kvm_host.h | 2 ++
arch/x86/kvm/kvm_cache_regs.h | 7 +++++++
arch/x86/kvm/mmu.c | 6 +++---
arch/x86/kvm/svm.c | 13 +++++++++----
arch/x86/kvm/vmx.c | 24 +++++++++++++++---------
arch/x86/kvm/x86.c | 19 ++++++++++---------
6 files changed, 46 insertions(+), 25 deletions(-)
next reply other threads:[~2010-12-05 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 17:01 Avi Kivity [this message]
2010-12-05 17:01 ` [PATCH 1/2] KVM: Replace reads of vcpu->arch.cr3 by an accessor Avi Kivity
2010-12-05 17:01 ` [PATCH 2/2] KVM: Fetch guest cr3 from hardware on demand Avi Kivity
2010-12-06 16:41 ` 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=1291568517-8717-1-git-send-email-avi@redhat.com \
--to=avi@redhat.com \
--cc=kvm@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