All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>,
	mtosatti@redhat.com, kvm@vger.kernel.org,
	yoshikawa.takuya@oss.ntt.co.jp
Subject: Re: [PATCH 1/5] KVM: x86 emulator: Use single stage decoding for Group 1 instructions
Date: Tue, 22 Mar 2011 14:53:21 +0200	[thread overview]
Message-ID: <4D889BC1.2010907@redhat.com> (raw)
In-Reply-To: <20110315230651.4ba2029c.takuya.yoshikawa@gmail.com>

On 03/15/2011 04:06 PM, Takuya Yoshikawa wrote:
> >  >  So I just decided to treat CMPS and SCAS in another patch.
> >  >  I mean I may introduce em_cmps or em_scas later if needed.
> >  >
> >  scas will likely just call em_cmp.
> >
> >  >  You prefer to treat these in this patch?
> >  >
> >  If there will be other patch for those instruction then it may be left
> >  as is.
>
> In my city, electric power supply may become restricted under control
> from now, though only a few hours.  So please take the patch series as
> is if possible!

I prefer to have the patchset fully updated, even if it takes a while.  
Good luck with the recovery!

> >  >
> >  >  What is the difference of CMPS and SCAS?
> >  >
> >  >
> >  One compares to memory locations and another memory with AX register.
>
> I wanted to know whether we should introduce em_cmps() or em_scas() later.
>
> Probably we can eliminate introducing em_scas() because it should be
> completely same as em_cmp().

I agree.

> But em_cmps() will be needed for inserting
>    c->dst.type = OP_NONE;
> before em_cmp().

I think we can put this line into em_cmp().  In fact, it looks like CMP 
r/m, reg will now write back the data into memory, which is wrong.  So I 
recommend a first patch to add c->dst.type = OP_NONE before the cmp: 
label, so we have a fix patch followed by a refactoring patch.

Later we can have a ReadOnly opcode table bit, so we can disable 
writeback from the opcode tables, not the code.


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


  reply	other threads:[~2011-03-22 12:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-13 15:15 [PATCH 0/5] KVM: x86 emulator: Use single stage decoding -- Part 1 Takuya Yoshikawa
2011-03-13 15:17 ` [PATCH 1/5] KVM: x86 emulator: Use single stage decoding for Group 1 instructions Takuya Yoshikawa
2011-03-14 15:11   ` Gleb Natapov
2011-03-14 21:32     ` Takuya Yoshikawa
2011-03-15  9:35       ` Gleb Natapov
2011-03-15 14:06         ` Takuya Yoshikawa
2011-03-22 12:53           ` Avi Kivity [this message]
2011-03-22 15:35             ` Takuya Yoshikawa
2011-03-22 15:53               ` Avi Kivity
2011-03-22 12:55   ` Avi Kivity
2011-03-22 15:37     ` Takuya Yoshikawa
2011-03-13 15:19 ` [PATCH 2/5] KVM: x86 emulator: Use single stage decoding for PUSH/POP XS instructions Takuya Yoshikawa
2011-03-22 13:03   ` Avi Kivity
2011-03-22 15:45     ` Takuya Yoshikawa
2011-03-13 15:20 ` [PATCH 3/5] KVM: x86 emulator: Use single stage decoding for POP instructions Takuya Yoshikawa
2011-03-22 13:06   ` Avi Kivity
2011-03-22 15:49     ` Takuya Yoshikawa
2011-03-13 15:21 ` [PATCH 4/5] KVM: x86 emulator: Use single stage decoding for PUSHA and POPA instructions Takuya Yoshikawa
2011-03-22 13:07   ` Avi Kivity
2011-03-22 15:54     ` Takuya Yoshikawa
2011-03-22 16:34       ` Avi Kivity
2011-03-13 15:23 ` [PATCH 5/5] KVM: x86 emulator: Use single stage decoding for PUSHF and POPF instructions Takuya Yoshikawa

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=4D889BC1.2010907@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=takuya.yoshikawa@gmail.com \
    --cc=yoshikawa.takuya@oss.ntt.co.jp \
    /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.