From: Gleb Natapov <gleb@redhat.com>
To: Arthur Chunqi Li <yzt356@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, kvm <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@web.de>
Subject: Re: How to recreate MOV-SS blocking vmentry fail
Date: Wed, 11 Sep 2013 16:44:09 +0300 [thread overview]
Message-ID: <20130911134409.GF17294@redhat.com> (raw)
In-Reply-To: <CABpY8ML8SiDMDLWVSEG1P--wy4Ur3tiVgKr35mP7Fun_quB4Sg@mail.gmail.com>
On Wed, Sep 11, 2013 at 09:04:26PM +0800, Arthur Chunqi Li wrote:
> On Wed, Sep 11, 2013 at 9:03 PM, Gleb Natapov <gleb@redhat.com> wrote:
> > On Wed, Sep 11, 2013 at 03:01:07PM +0200, Paolo Bonzini wrote:
> >> Il 11/09/2013 14:53, Gleb Natapov ha scritto:
> >> >> > I was trying to recreate MOV-SS blocking vmentry fail (Intel SDM 26.1,
> >> >> > 5. a). Here the manual refers to Table 24-3, but later in 26.3.1.5
> >> >> > also describe it. I got confused how this scenario can be recreated.
> >> >> > Do you have any ideas?
> >> >> >
> >> > mov $0, %ss
> >> > vmlaunch
> >>
> >> Probably better to save %ss somewhere around these instructions... :)
> >>
> > Details, details :) It can be:
> > mov %ss, tmp
> > mov tmp, $ss
> > vmlaunch
> Well, this seems hard to test this in our framework ;( vmlaunch is
> surrounded with many instructions and we cannot add vmlaunch in exit
> handler.
>
Well, we can put moves always there, or write special test for it, but it
is nice to have test, but not very important.
--
Gleb.
prev parent reply other threads:[~2013-09-11 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 12:49 How to recreate MOV-SS blocking vmentry fail Arthur Chunqi Li
2013-09-11 12:53 ` Gleb Natapov
2013-09-11 12:55 ` Arthur Chunqi Li
2013-09-11 12:57 ` Gleb Natapov
2013-09-11 13:01 ` Paolo Bonzini
2013-09-11 13:03 ` Gleb Natapov
2013-09-11 13:04 ` Arthur Chunqi Li
2013-09-11 13:44 ` Gleb Natapov [this message]
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=20130911134409.GF17294@redhat.com \
--to=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=yzt356@gmail.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.