From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Vendor specific instructions and the emulator
Date: Fri, 4 Feb 2011 11:25:24 -0200 [thread overview]
Message-ID: <20110204132523.GA10492@amt.cnet> (raw)
In-Reply-To: <1296570724-18383-1-git-send-email-avi@redhat.com>
On Tue, Feb 01, 2011 at 04:32:01PM +0200, Avi Kivity wrote:
> 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
> v3: preserve early-exit on #UD (reexecute_instruction() isn't reliable
> since we don't have a valid cr2)
>
> arch/x86/include/asm/kvm_emulate.h | 1 +
> arch/x86/kvm/emulate.c | 12 +++++++++---
> arch/x86/kvm/x86.c | 36 +++++-------------------------------
> 3 files changed, 15 insertions(+), 34 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2011-02-04 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 14:32 [PATCH v3 0/3] Vendor specific instructions and the emulator Avi Kivity
2011-02-01 14:32 ` [PATCH v3 1/3] KVM: Drop bogus x86_decode_insn() error check Avi Kivity
2011-02-01 14:32 ` [PATCH v3 2/3] KVM: x86 emulator: vendor specific instructions Avi Kivity
2011-02-01 14:32 ` [PATCH v3 3/3] KVM: Drop ad-hoc vendor specific instruction restriction Avi Kivity
2011-02-04 13:25 ` Marcelo Tosatti [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=20110204132523.GA10492@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).