From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: avi@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, 15 Mar 2011 23:06:51 +0900 [thread overview]
Message-ID: <20110315230651.4ba2029c.takuya.yoshikawa@gmail.com> (raw)
In-Reply-To: <20110315093507.GU10151@redhat.com>
On Tue, 15 Mar 2011 11:35:07 +0200
Gleb Natapov <gleb@redhat.com> wrote:
> > > Why not call em_cmp() here?
> >
> > I thought that I needed to check of
> > c->dst.type = OP_NONE; /* Disable writeback. */
> > later.
> >
> I mean call em_cmp() after c->dst.type = OP_NONE line, not replacing it.
I see the point!
> > 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!
>
> > > > + break;
> > > > case 0xa8 ... 0xa9: /* test ax, imm */
> > > > goto test;
> > > > case 0xae ... 0xaf: /* scas */
> > > > - goto cmp;
> > > > + emulate_2op_SrcV("cmp", c->src, c->dst, ctxt->eflags);
> > > And here?
> >
> > 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().
But em_cmps() will be needed for inserting
c->dst.type = OP_NONE;
before em_cmp().
Anyway, I will submit a patch for CMPS and SCAS conversion separately
if this patch can be applied.
Thanks,
Takuya
>
> --
> Gleb.
next prev parent reply other threads:[~2011-03-15 14:06 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 [this message]
2011-03-22 12:53 ` Avi Kivity
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=20110315230651.4ba2029c.takuya.yoshikawa@gmail.com \
--to=takuya.yoshikawa@gmail.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox