From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: [PATCH 0/2] Segment cleanups and optimizations
Date: Thu, 28 Apr 2011 12:23:19 +0300 [thread overview]
Message-ID: <1303982601-30666-1-git-send-email-avi@redhat.com> (raw)
The first patch in this segment-themed patchset cleans up segment handling
in the emulator; while the second patch undoes some of the performance hit
taken by the emulator segment limit checks.
Avi Kivity (2):
KVM: x86 emulator: consolidate segment accessors
KVM: VMX: Cache vmcs segment fields
arch/x86/include/asm/kvm_emulate.h | 13 +---
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/emulate.c | 122 ++++++++++++++++++++----------------
arch/x86/kvm/vmx.c | 102 +++++++++++++++++++++++++++---
arch/x86/kvm/x86.c | 41 +++---------
5 files changed, 176 insertions(+), 103 deletions(-)
--
1.7.4.3
next reply other threads:[~2011-04-28 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 9:23 Avi Kivity [this message]
2011-04-28 9:23 ` [PATCH 1/2] KVM: x86 emulator: consolidate segment accessors Avi Kivity
2011-04-28 9:23 ` [PATCH 2/2] KVM: VMX: Cache vmcs segment fields 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=1303982601-30666-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