public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] KVM: x86 emulator: don't update vcpu state if instruction is restarted.
Date: Mon, 2 Aug 2010 10:58:38 +0300	[thread overview]
Message-ID: <20100802075838.GL24773@redhat.com> (raw)
In-Reply-To: <4C5651D4.7060905@redhat.com>

On Mon, Aug 02, 2010 at 08:04:20AM +0300, Avi Kivity wrote:
>  On 08/01/2010 04:27 PM, Gleb Natapov wrote:
> >
> >When we are going to enable e_i_g_s by default?
> 
> Optimistically, 2.6.37, so six months.
> 
> >May be we have enough
> >time to fix userspace?
> 
> Sure we do, but will users update?
> 
> 0.12 is mature enough that some users will forget about it and not
> update it.
> 
So they will not update kernel too. 0.12/2.6.32 should be mature combo.
And we can add patch to 0.12/0.13 stable to work on newer kernels. But
realistically the problem will occur only if TPR access is done from big
real mode by Windows XP running on old Intel cpus. What are the chances
that this will be a problem in practice?

> >Too ancient userspace already does not run on recent
> >kvm. Or may be we can make userspace enable e_i_g_s per guest. This way
> >userspace that knows it is OK can tell kernel so.
> 
> Let's make it the other way round, enable the optimization for
> userspace that declares that it does not make use of rip during
> emulation (kvm-tpr-opt can be changed by queueing a signal and
> re-entering the guest to complete the operation).
> 
> Later we can make the optimization unconditional.
> 
What do you call "optimization"? e_i_g_s=1? Isn't it the same as I proposed
then?

--
			Gleb.

  reply	other threads:[~2010-08-02  7:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 12:11 [PATCH 0/2] Speedup ins instruction emulation a little Gleb Natapov
2010-07-29 12:11 ` [PATCH 1/2] KVM: x86 emulator: don't update vcpu state if instruction is restarted Gleb Natapov
2010-07-31 17:25   ` Avi Kivity
2010-08-01  8:28     ` Gleb Natapov
2010-08-01  8:54       ` Avi Kivity
2010-08-01  9:01         ` Gleb Natapov
2010-08-01  9:14           ` Avi Kivity
2010-08-01  9:24             ` Gleb Natapov
2010-08-01 10:00               ` Avi Kivity
2010-08-01 10:53                 ` Gleb Natapov
2010-08-01 12:17                   ` Avi Kivity
2010-08-01 12:23                     ` Gleb Natapov
2010-08-01 12:35                       ` Avi Kivity
2010-08-01 13:27                         ` Gleb Natapov
2010-08-02  5:04                           ` Avi Kivity
2010-08-02  7:58                             ` Gleb Natapov [this message]
2010-08-02  8:03                               ` Avi Kivity
2010-08-02  8:17                                 ` Gleb Natapov
2010-08-02  8:24                                   ` Avi Kivity
2010-08-02  8:34                                     ` Gleb Natapov
2010-08-02  8:54                                       ` Avi Kivity
2010-08-02  9:05                                         ` Gleb Natapov
2010-08-02  9:08                                           ` Avi Kivity
2010-07-29 12:11 ` [PATCH 2/2] KVM: x86 emulator: check io permissions only once for string pio Gleb Natapov
2010-07-31  1:59   ` Marcelo Tosatti
2010-07-29 12:19 ` [PATCH 0/2] Speedup ins instruction emulation a little 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=20100802075838.GL24773@redhat.com \
    --to=gleb@redhat.com \
    --cc=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