public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: about vEOI optimization
Date: Wed, 24 Aug 2011 13:00:11 +0300	[thread overview]
Message-ID: <4E54CBAB.5070401@redhat.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F150630051F1F5@shsmsx502.ccr.corp.intel.com>

On 08/23/2011 11:09 AM, Tian, Kevin wrote:
> Hi, Avi,
>
> Both Eddie and Marcello once suggested vEOI optimization by skipping
> heavy-weight instruction decode, which reduces vEOI overhead greatly:
>
> http://www.mail-archive.com/kvm@vger.kernel.org/msg18619.html
> http://www.spinics.net/lists/kvm/msg36691.html
>
> Though virtual x2apic serves similar purpose, it depends on guest OS
> to support x2apic. Many Windows versions don't support x2apic though,
> including Win7, Windows server before 2008 R2, etc. Given that virtualization
> need support various OS versions, any chance to incorporate above vEOI
> optimization in KVM as an alternative to boost performance when guest
> doesn't support x2apic?
>

Yes.  There was a problem with the guest using MOVSD or STOSD to write 
the EOI; if we don't emulate, then registers don't get updated.  I guess 
we can ignore it since no sane guest will use those instructions for EOI.

Another option is the hyper-V EOI support, which can also eliminate the 
EOI exit when no additional interrupt is pending.  This can improve EOI 
performance even more.


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2011-08-24 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23  8:09 about vEOI optimization Tian, Kevin
2011-08-24 10:00 ` Avi Kivity [this message]
2011-08-25  2:24   ` Tian, Kevin
2011-08-25  4:39     ` 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=4E54CBAB.5070401@redhat.com \
    --to=avi@redhat.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    /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