From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alexandru Duţu" <alex.dutu@gmail.com>, kvm@vger.kernel.org
Subject: Re: KVM exit on UD interception
Date: Tue, 06 May 2014 18:56:38 +0200 [thread overview]
Message-ID: <53691446.7070706@redhat.com> (raw)
In-Reply-To: <CAEKRH4EYZApPFw6P7xociS7npxzMFgzppv7Ay9k92=ihhf+U-Q@mail.gmail.com>
Il 05/05/2014 17:56, Alexandru Duţu ha scritto:
>
> It seems that re-entering virtualized execution on UD interception
> gives the user the flexibility of running binaries with newer
> instructions on older hardware, if kvm is able to emulate the newer
> instructions. I do not fully understand the details of this scenario,
> is there such a scenario or is it likely that ud_interception() will
> change?
Yes, you are correct. This emulation capability is used in some cases,
including: MOVBE, SYSCALL/SYSENTER on 32-bit guests, VMCALL and VMMCALL.
Paolo
next prev parent reply other threads:[~2014-05-06 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 15:56 KVM exit on UD interception Alexandru Duţu
2014-05-05 17:34 ` Nakajima, Jun
2014-05-05 18:48 ` Alexandru Duţu
2014-05-06 0:07 ` Nakajima, Jun
2014-05-06 0:47 ` Alexandru Duţu
2014-05-06 16:56 ` Paolo Bonzini [this message]
2014-05-06 20:11 ` Alexandru Duţu
2014-05-07 6:55 ` Paolo Bonzini
2014-05-08 3:30 ` Alexandru Duţu
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=53691446.7070706@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.dutu@gmail.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 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.