kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86 emulator: re-implementing 'mov AL,moffs' 	instruction decoding
Date: Wed, 07 Jul 2010 17:36:42 +0800	[thread overview]
Message-ID: <4C344AAA.2060904@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTincWSmCiVs7huNMyD5IT3WcmkeOh6I-ZKU-Jvlw@mail.gmail.com>


> 2010/7/7 Wei Yongjun <yjwei@cn.fujitsu.com>:
>   
>> This patch change to use DstAcc for decoding 'mov AL, moffs'
>> and introduced SrcAcc for decoding 'mov moffs, AL'.
>>
>> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
>> ---
>>  arch/x86/kvm/emulate.c |   30 +++++++++++++++++++++++-------
>>  1 files changed, 23 insertions(+), 7 deletions(-)
>>
>> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
>> index 99fa1c7..87289c2 100644
>> --- a/arch/x86/kvm/emulate.c
>> +++ b/arch/x86/kvm/emulate.c
>> @@ -70,6 +70,7 @@
>>  #define SrcSI       (0xa<<4)   /* Source is in the DS:RSI */
>>  #define SrcImmFAddr (0xb<<4)   /* Source is immediate far address */
>>  #define SrcMemFAddr (0xc<<4)   /* Source is far address in memory */
>> +#define SrcAcc      (0xd<<4)   /* Source Accumulator */
>>  #define SrcMask     (0xf<<4)
>>  /* Generic ModRM decode. */
>>  #define ModRM       (1<<8)
>> @@ -177,8 +178,8 @@ static u32 opcode_table[256] = {
>>        0, 0, SrcImmFAddr | No64, 0,
>>        ImplicitOps | Stack, ImplicitOps | Stack, 0, 0,
>>        /* 0xA0 - 0xA7 */
>> -       ByteOp | SrcMem | Mov | MemAbs, SrcMem | Mov | MemAbs,
>> -       ByteOp | DstMem | Mov | MemAbs, DstMem | Mov | MemAbs,
>> +       ByteOp | DstAcc | SrcMem | Mov | MemAbs, DstAcc | SrcMem | Mov | MemAbs,
>> +       ByteOp | DstMem | SrcAcc | Mov | MemAbs, DstMem | SrcAcc | Mov | MemAbs,
>>        ByteOp | SrcSI | DstDI | Mov | String, SrcSI | DstDI | Mov | String,
>>        ByteOp | SrcSI | DstDI | String, SrcSI | DstDI | String,
>>        /* 0xA8 - 0xAF */
>> @@ -1186,6 +1187,25 @@ done_prefixes:
>>                else
>>                        c->src.val = insn_fetch(u8, 1, c->eip);
>>                break;
>> +       case SrcAcc:
>> +               c->src.type = OP_REG;
>> +               c->src.bytes = (c->d & ByteOp) ? 1 : c->op_bytes;
>> +               c->src.ptr = &c->regs[VCPU_REGS_RAX];
>> +               switch (c->src.bytes) {
>> +                       case 1:
>> +                               c->src.val = *(u8 *)c->src.ptr;
>> +                               break;
>> +                       case 2:
>> +                               c->src.val = *(u16 *)c->src.ptr;
>> +                               break;
>> +                       case 4:
>> +                               c->src.val = *(u32 *)c->src.ptr;
>> +                               break;
>> +                       case 8:
>> +                               c->src.val = *(u64 *)c->src.ptr;
>> +                               break;
>> +               }
>> +               break;
>>        case SrcOne:
>>                c->src.bytes = 1;
>>                c->src.val = 1;
>> @@ -2854,13 +2874,9 @@ special_insn:
>>                if (rc != X86EMUL_CONTINUE)
>>                        goto done;
>>                break;
>> -       case 0xa0 ... 0xa1:     /* mov */
>> -               c->dst.ptr = (unsigned long *)&c->regs[VCPU_REGS_RAX];
>> +       case 0xa0 ... 0xa3:     /* mov */
>>                c->dst.val = c->src.val;
>>                break;
>> -       case 0xa2 ... 0xa3:     /* mov */
>> -               c->dst.val = (unsigned long)c->regs[VCPU_REGS_RAX];
>> -               break;
>>        case 0xa4 ... 0xa5:     /* movs */
>>                goto mov;
>>     
> Instead of duplicating the mov code, you could've changed the case
> statement to handle 0xa0...0xa5 which will jump to the "mov" label
> anyway. The decoder flags will correctly handle src and dst values.
>   

good idea, I will fix this, thanks.

>
>
>   

  reply	other threads:[~2010-07-07  9:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06  8:49 [PATCH 1/6] KVM: x86 emulator: fix 'mov sreg,rm16' instruction decoding Wei Yongjun
2010-07-06  8:50 ` [PATCH 2/6] KVM: x86 emulator: fix the comment of out instruction Wei Yongjun
2010-07-06  8:51 ` [PATCH 3/6] KVM: x86 emulator: fix 'and AL,imm8' instruction decoding Wei Yongjun
2010-07-06  8:52 ` [PATCH 4/6] KVM: x86 emulator: fix 'mov rm,sreg' " Wei Yongjun
2010-07-06  8:53 ` [PATCH 5/6] KVM: x86 emulator: fix 'mov AL,moffs' " Wei Yongjun
2010-07-06 11:57   ` Avi Kivity
2010-07-07  6:25     ` Wei Yongjun
2010-07-07  6:26     ` [PATCH] KVM: x86 emulator: re-implementing " Wei Yongjun
2010-07-07  9:33       ` Mohammed Gamal
2010-07-07  9:36         ` Wei Yongjun [this message]
2010-07-07  9:43       ` [PATCHv2] " Wei Yongjun
2010-07-07  9:50         ` Avi Kivity
2010-07-06  8:54 ` [PATCH 6/6] KVM: x86 emulator: fix cli/sti instruction emulation Wei Yongjun
2010-07-06  9:22 ` [PATCH 1/6] KVM: x86 emulator: fix 'mov sreg,rm16' instruction decoding 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=4C344AAA.2060904@cn.fujitsu.com \
    --to=yjwei@cn.fujitsu.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=m.gamal005@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).