From: Avi Kivity <avi@redhat.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH non-atomic-injection] x86 emulator: Add 2 operand imul instruction (opcode 0x0f 0xaf)
Date: Wed, 18 Aug 2010 20:56:18 +0300 [thread overview]
Message-ID: <4C6C1EC2.9030106@redhat.com> (raw)
In-Reply-To: <1282153210-4309-1-git-send-email-m.gamal005@gmail.com>
On 08/18/2010 08:40 PM, Mohammed Gamal wrote:
> Signed-off-by: Mohammed Gamal<m.gamal005@gmail.com>
> ---
> arch/x86/kvm/emulate.c | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> index cb3282c..3311c68 100644
> --- a/arch/x86/kvm/emulate.c
> +++ b/arch/x86/kvm/emulate.c
> @@ -2474,7 +2474,7 @@ static struct opcode twobyte_table[256] = {
> N, D(DstMem | SrcReg | ModRM | BitOp | Lock),
> D(DstMem | SrcReg | Src2ImmByte | ModRM),
> D(DstMem | SrcReg | Src2CL | ModRM),
> - D(ModRM), N,
> + D(ModRM), D(DstReg | SrcMem | ModRM),
> /* 0xB0 - 0xB7 */
> D(ByteOp | DstMem | SrcReg | ModRM | Lock), D(DstMem | SrcReg | ModRM | Lock),
> N, D(DstMem | SrcReg | ModRM | BitOp | Lock),
> @@ -3567,6 +3567,9 @@ twobyte_insn:
> break;
> case 0xae: /* clflush */
> break;
> + case 0xaf:
> + emulate_2op_SrcV_nobyte("imul", c->src, c->dst, ctxt->eflags);
> + break;
> case 0xb0 ... 0xb1: /* cmpxchg */
> /*
> * Save real source value, then compare EAX against
I already added this, please look at the non-atomic-injection branch.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-08-18 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 17:40 [PATCH non-atomic-injection] x86 emulator: Add 2 operand imul instruction (opcode 0x0f 0xaf) Mohammed Gamal
2010-08-18 17:56 ` Avi Kivity [this message]
2010-08-18 18:04 ` Mohammed Gamal
2010-08-18 19:25 ` Mohammed Gamal
2010-08-19 6:38 ` Avi Kivity
2010-08-19 13:09 ` Mohammed Gamal
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=4C6C1EC2.9030106@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox