public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, <kvm@vger.kernel.org>,
	<mtosatti@redhat.com>
Subject: Re: [PATCH 2/2] Provide fast path for "rep ins" emulation if possible.
Date: Thu, 24 May 2012 12:54:03 +0200	[thread overview]
Message-ID: <20120524105403.GL2604@amd.com> (raw)
In-Reply-To: <4FBE0F43.4060408@redhat.com>

On Thu, May 24, 2012 at 01:36:51PM +0300, Avi Kivity wrote:
> On 05/24/2012 01:34 PM, Roedel, Joerg wrote:
> > On Wed, May 23, 2012 at 05:49:31PM +0300, Avi Kivity wrote:
> >> On 05/23/2012 05:40 PM, Avi Kivity wrote:
> >> > On 05/23/2012 05:08 PM, Gleb Natapov wrote:
> >> > If decode assists are not available, we still need to emulate, see 15.33.5.
> >> > 
> >> 
> >> Joerg, the 2010 version of the manual says that the effective segment
> >> (10:12) is only available with decode assists.  The 2012 version says
> >> it's unconditional. What's correct?
> > 
> > It is still conditional and only available with decode-assists. I will
> > talk to the APM authors to clarify this in the documentation.
> 
> Thanks.  As it happens it doesn't matter for INS emulation, only OUTS,
> unless other bits in that word also depend on decode assists.

Doesn't look like it. All other bits EXITINFO1 bits for the IOIO
intercept are documented from the very ancient beginnings of SVM. So the
segment number is the only addition.


	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632


  reply	other threads:[~2012-05-24 10:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 14:08 [PATCH 0/2] improve speed of "rep ins" emulation Gleb Natapov
2012-05-23 14:08 ` [PATCH 1/2] Provide userspace IO exit completion callback Gleb Natapov
2012-05-23 14:08 ` [PATCH 2/2] Provide fast path for "rep ins" emulation if possible Gleb Natapov
2012-05-23 14:40   ` Avi Kivity
2012-05-23 14:49     ` Avi Kivity
2012-05-24 10:34       ` Roedel, Joerg
2012-05-24 10:36         ` Avi Kivity
2012-05-24 10:54           ` Roedel, Joerg [this message]
2012-06-05 17:27             ` Alexander Graf
2012-06-05 17:36               ` Gleb Natapov
2012-06-05 17:41                 ` Alexander Graf
2012-06-05 17:50                   ` Gleb Natapov
2012-06-05 18:17                     ` Gleb Natapov
2012-06-05 17:57                   ` Gleb Natapov
2012-06-06  9:28                     ` Roedel, Joerg
2012-06-05 16:07   ` Avi Kivity
2012-06-05 17:19     ` Gleb Natapov
2012-06-06  8:04       ` 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=20120524105403.GL2604@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=avi@redhat.com \
    --cc=gleb@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