public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 7/8] KVM: x86 emulator: simplify instruction decode flags for opcodes E0-FF
Date: Mon, 23 Aug 2010 16:46:01 +0300	[thread overview]
Message-ID: <4C727B99.40408@redhat.com> (raw)
In-Reply-To: <20100823133303.GQ10499@redhat.com>

  On 08/23/2010 04:33 PM, Gleb Natapov wrote:
> On Mon, Aug 23, 2010 at 02:06:16PM +0300, Avi Kivity wrote:
>> Use the new byte/word dual opcode decode.
>>
>> Signed-off-by: Avi Kivity<avi@redhat.com>
>> ---
>>   arch/x86/kvm/emulate.c |    6 ++----
>>   1 files changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
>> index c61f73d..6cb5663 100644
>> --- a/arch/x86/kvm/emulate.c
>> +++ b/arch/x86/kvm/emulate.c
>> @@ -2464,13 +2464,11 @@ static struct opcode opcode_table[256] = {
>>   	N, N, N, N, N, N, N, N,
>>   	/* 0xE0 - 0xE7 */
>>   	X3(D(SrcImmByte)), N,
>> -	D(ByteOp | SrcImmUByte | DstAcc), D(SrcImmUByte | DstAcc),
>> -	D(ByteOp | SrcAcc | DstImmUByte), D(SrcAcc | DstImmUByte),
>> +	D2bv(SrcImmUByte | DstAcc), D2bv(SrcAcc | DstImmUByte),
>>   	/* 0xE8 - 0xEF */
>>   	D(SrcImm | Stack), D(SrcImm | ImplicitOps),
>>   	D(SrcImmFAddr | No64), D(SrcImmByte | ImplicitOps),
>> -	D(SrcNone | ByteOp | DstAcc), D(SrcNone | DstAcc),
>> -	D(ByteOp | SrcAcc | ImplicitOps), D(SrcAcc | ImplicitOps),
>> +	D2bv(SrcNone | DstAcc),	D2bv(SrcAcc | ImplicitOps),
>>   	/* 0xF0 - 0xF7 */
>>   	N, N, N, N,
>>   	D(ImplicitOps | Priv), D(ImplicitOps), G(ByteOp, group3), G(0, group3),
> Hmm. I actually have a patch that makes encoding of those to be different.
>
> ===
>      Some instructions has 32 bit operand even in long mode.
>
>      Decode this through decode table instead of during instruction
>      emulation.
>

This can still work.

> @@ -2750,6 +2751,9 @@ done_prefixes:
>   			c->op_bytes = 4;
>   	}
>
> +	if (mode == X86EMUL_MODE_PROT64&&  (c->d&  Op32in64))
> +		c->op_bytes = 4;

Just check that it isn't a ByteOp.

btw, shouldn't that be

     if (c->op_bytes == 8 && (c->d & Op32in64))

?  to account for c->op_bytes = 2 initially.


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-08-23 13:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 11:06 [PATCH 0/8] Simplify byte/word opcode pair decode Avi Kivity
2010-08-23 11:06 ` [PATCH 1/8] KVM: x86 emulator: support byte/word opcode pairs Avi Kivity
2010-08-23 11:06 ` [PATCH 2/8] KVM: x86 emulator: simplify ALU block (opcodes 00-3F) decode flags Avi Kivity
2010-08-25 19:39   ` Marcelo Tosatti
2010-08-26  8:26     ` Avi Kivity
2010-08-23 11:06 ` [PATCH 3/8] KVM: x86 emulator: simplify string instruction " Avi Kivity
2010-08-23 11:06 ` [PATCH 4/8] KVM: x86 emulator: simplify instruction decode flags for opcodes 80-8F Avi Kivity
2010-08-23 11:06 ` [PATCH 5/8] KVM: x86 emulator: simplify instruction decode flags for opcodes A0-AF Avi Kivity
2010-08-23 11:06 ` [PATCH 6/8] KVM: x86 emulator: simplify instruction decode flags for opcodes C0-DF Avi Kivity
2010-08-23 11:06 ` [PATCH 7/8] KVM: x86 emulator: simplify instruction decode flags for opcodes E0-FF Avi Kivity
2010-08-23 13:33   ` Gleb Natapov
2010-08-23 13:46     ` Avi Kivity [this message]
2010-08-23 13:56       ` Gleb Natapov
2010-08-23 11:06 ` [PATCH 8/8] KVM: x86 emulator: simplify instruction decode flags for opcodes 0F 00-FF Avi Kivity
2010-08-23 13:29 ` [PATCH 0/8] Simplify byte/word opcode pair decode Paolo Bonzini
2010-08-23 13:48   ` Avi Kivity
2010-08-23 14:04     ` Paolo Bonzini
2010-08-23 14:13       ` 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=4C727B99.40408@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@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