From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: [PATCH v2 0/3] Vendor specific instructions and the emulator
Date: Tue, 1 Feb 2011 14:43:56 +0200 [thread overview]
Message-ID: <1296564239-14163-1-git-send-email-avi@redhat.com> (raw)
Currently we have some ad-hoc code in x86.c to restrict #UD emulation to
expected instructions (that is, vendor specific instructions). This patchset
replaces the ad-hoc code with proper emulator support using decode tables.
Avi Kivity (3):
KVM: Drop bogus x86_decode_insn() error check
v2: replaces v1's first two patches
KVM: x86 emulator: vendor specific instructions
KVM: Drop ad-hoc vendor specific instruction restriction
arch/x86/include/asm/kvm_emulate.h | 1 +
arch/x86/kvm/emulate.c | 12 +++++++++---
arch/x86/kvm/x86.c | 34 +++-------------------------------
3 files changed, 13 insertions(+), 34 deletions(-)
next reply other threads:[~2011-02-01 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 12:43 Avi Kivity [this message]
2011-02-01 12:43 ` [PATCH v2 1/3] KVM: Drop bogus x86_decode_insn() error check Avi Kivity
2011-02-01 12:43 ` [PATCH v2 2/3] KVM: x86 emulator: vendor specific instructions Avi Kivity
2011-02-01 12:43 ` [PATCH v2 3/3] KVM: Drop ad-hoc vendor specific instruction restriction 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=1296564239-14163-1-git-send-email-avi@redhat.com \
--to=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