qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Richard Henderson <rth@twiddle.net>,
	Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>,
	qemu-devel@nongnu.org
Cc: fred.konrad@greensocs.com, zealot351@gmail.com,
	maria.klimushenkova@ispras.ru, mark.burton@greensocs.com,
	batuzovk@ispras.ru
Subject: Re: [Qemu-devel] [PATCH] i386: fix icount processing for repz instructions
Date: Thu, 23 Oct 2014 22:19:15 +0200	[thread overview]
Message-ID: <544962C3.6040404@redhat.com> (raw)
In-Reply-To: <54493557.2040106@twiddle.net>



On 10/23/2014 07:05 PM, Richard Henderson wrote:
> On 10/21/2014 06:03 AM, Pavel Dovgalyuk wrote:
>> +    dc->repz_opt = dc->jmp_opt
>> +                    /* Do not optimize repz jumps at all in icount mode, because
>> +                       rep movsS instructions are execured with different paths
>> +                       in repz_opt and !repz_opt modes. The first one was used
>> +                       always except single step mode. And this setting
>> +                       disables jumps optimization and control paths become
>> +                       equivalent in run and single step modes.
>> +                       Now there will be no jump optimization for repz in
>> +                       trace and replay modes and there will always be an
>> +                       additional step for ecx=0.
>> +                     */
>> +                   || use_icount;
> 
> My aesthetics are offended by the placement of this comment.  Please write
> 
>   /* Comment */
>   dc->repz_opt = x || y;
> 
> That said, surely that test should be !use_icount.

And "&& !use_icount", even (it becomes "|| use_icount" in the ifs)?

Paolo

      reply	other threads:[~2014-10-23 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 13:03 [Qemu-devel] [PATCH] i386: fix icount processing for repz instructions Pavel Dovgalyuk
2014-10-23 17:05 ` Richard Henderson
2014-10-23 20:19   ` Paolo Bonzini [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=544962C3.6040404@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=batuzovk@ispras.ru \
    --cc=fred.konrad@greensocs.com \
    --cc=maria.klimushenkova@ispras.ru \
    --cc=mark.burton@greensocs.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=zealot351@gmail.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).