All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Guillaume Thouvenin <guillaume.thouvenin@ext.bull.net>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] x86 emulator: Add a Src2 decode set and SrcOne operand type
Date: Wed, 22 Oct 2008 12:29:48 +0200	[thread overview]
Message-ID: <48FF009C.5030705@redhat.com> (raw)
In-Reply-To: <20081009132359.0602a8d2@frecb000711>

Guillaume Thouvenin wrote:
>  Instruction like shld has three operands, so we need to add a Src2
> decode set. We start with Src2None, Src2CL, and Src2Imm8 to support
> shld and we will expand it later. Operand type of Src2 are placed at
> the end of the set to avoid renumbering. For Src2CL we mask to a single
> byte and set the operand length.
>
>  This patch also added SrcOne operand type when we need to decode an
> implied '1' like with regular shift instruction. 
>
>   

Looks fine; I will apply when shld/shrd are ready.

>  If needed I can split this patch into two patches, one for Src2 decode
> set and another one for SrcOne. 
>   

Maybe even three: extend the opcode descriptor to 32 bits, add SrcOne, 
add Src2*.

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


      reply	other threads:[~2008-10-22 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 12:52 Emulation of shld instruction doesn't work Guillaume Thouvenin
2008-10-08 13:05 ` Guillaume Thouvenin
2008-10-08 14:14 ` Avi Kivity
2008-10-09  7:52   ` [PATCH] x86 emulator: Add Src2 decode set Guillaume Thouvenin
2008-10-09  8:11     ` Avi Kivity
2008-10-09  8:24       ` Avi Kivity
2008-10-09  8:57       ` Guillaume Thouvenin
2008-10-09  9:06         ` Avi Kivity
2008-10-09  9:30           ` Guillaume Thouvenin
2008-10-09 11:23       ` [PATCH] x86 emulator: Add a Src2 decode set and SrcOne operand type Guillaume Thouvenin
2008-10-22 10:29         ` Avi Kivity [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=48FF009C.5030705@redhat.com \
    --to=avi@redhat.com \
    --cc=guillaume.thouvenin@ext.bull.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.