From: Avi Kivity <avi@redhat.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [PATCH v2] KVM: APIC: avoid instruction emulation for EOI writes
Date: Tue, 30 Aug 2011 13:57:09 +0300 [thread overview]
Message-ID: <4E5CC205.9020806@redhat.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F15063045B0F67@shsmsx502.ccr.corp.intel.com>
On 08/30/2011 04:15 AM, Tian, Kevin wrote:
> v2 changes:
> define exit qualification fields for APIC-Access in vmx.h
> use apic_reg_write instead of apic_set_eoi, to avoid breaking tracing
> add fasteoi option to allow disabling this acceleration
>
> ----
>
> commit 2a66a12cb6928c962d24907e6d39b6eb9ac94b4b
> Author: Kevin Tian<kevin.tian@intel.com>
> Date: Mon Aug 29 13:08:28 2011 +0800
>
> KVM: APIC: avoid instruction emulation for EOI writes
>
> Instruction emulation for EOI writes can be skipped, since sane
> guest simply uses MOV instead of string operations. This is a nice
> improvement when guest doesn't support x2apic or hyper-V EOI
> support.
>
> a single VM bandwidth is observed with ~8% bandwidth improvement
> (7.4Gbps->8Gbps), by saving ~5% cycles from EOI emulation.
>
>
Thanks, applied. Please use git format-patch (and git send-email)
instead of git show in the future.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-08-30 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 1:15 [PATCH v2] KVM: APIC: avoid instruction emulation for EOI writes Tian, Kevin
2011-08-30 10:57 ` Avi Kivity [this message]
2011-08-31 0:12 ` Tian, Kevin
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=4E5CC205.9020806@redhat.com \
--to=avi@redhat.com \
--cc=eddie.dong@intel.com \
--cc=jan.kiszka@siemens.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.