qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "poletaev" <Dmitry.Poletaev@ispras.ru>
To: 'Stefan Hajnoczi' <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] improve emulation correctness
Date: Tue, 6 May 2014 16:16:38 +0400	[thread overview]
Message-ID: <000301cf6925$09817820$1c846860$@Poletaev@ispras.ru> (raw)
In-Reply-To: <20140502090901.GE8005@stefanha-thinkpad.redhat.com>

Thank you for attention :)
This patch not needed, according to QEMU dev policy, and so I will not sent
it any more. 
I found another defect, and it not related with undefined flags.

-----Original Message-----
From: Stefan Hajnoczi [mailto:stefanha@gmail.com] 
Sent: Friday, May 02, 2014 1:09 PM
To: poletaev
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] improve emulation correctness

On Thu, Apr 24, 2014 at 12:35:24PM +0400, poletaev wrote:
> There is a set of test, that checks QEMU CPU for similar behavior with 
> real hardware (http://roberto.greyhats.it/projects/pills.html). Test 
> reg/pill2579.c can detect, that program is execute in emulated
environment.
> It is related with behavior of rcl instruction. If the number of 
> shifted bits more than 1, OF of eflags become undefined. Real CPUs 
> does not change OF, if it is undefined. QEMU do it anyway.
> 
> Emulated program can execute that test and after that can understand 
> environment not real.
> 
>  
> 
> Signed-off-by: Dmitry Poletaev <observercool@gmail.com>

I see you resent the patch and it received attention the second time :).

Stefan

      reply	other threads:[~2014-05-06 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <535a981f.86a6e00a.7dc9.5f5cSMTPIN_ADDED_BROKEN@mx.google.com>
2014-05-02  9:04 ` [Qemu-devel] [PATCH] improve emulation correctness Stefan Hajnoczi
2014-05-02  9:09 ` Stefan Hajnoczi
2014-05-06 12:16   ` poletaev [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='000301cf6925$09817820$1c846860$@Poletaev@ispras.ru' \
    --to=dmitry.poletaev@ispras.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).