From: Paolo Bonzini <pbonzini@redhat.com>
To: Javier Picorel <javier.picorel@epfl.ch>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU: DBT vs. Interpretation
Date: Wed, 28 Jan 2015 14:40:53 +0100 [thread overview]
Message-ID: <54C8E6E5.6000005@redhat.com> (raw)
In-Reply-To: <6AAC1A89-731A-49B8-A96A-FB1AC02D9F9B@epfl.ch>
On 26/01/2015 21:54, Javier Picorel wrote:
> Hi,
>
> We are trying to make QEMU deterministic for
> architectural simulation. In the absence of I/O,
> let’s say only executing user code or exceptions,
> is there any source of indeterminism (e.g., non
> deterministic compiler optimizations, TB indeterminism)
> of QEMU’s DBT versus a canonical interpreter? Thanks!
No, there isn't.
Paolo
next prev parent reply other threads:[~2015-01-28 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 20:54 [Qemu-devel] QEMU: DBT vs. Interpretation Javier Picorel
2015-01-28 13:40 ` Paolo Bonzini [this message]
2015-01-28 15:10 ` Laurent Desnogues
2015-01-28 15:39 ` Peter Maydell
2015-01-28 15:53 ` Laurent Desnogues
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=54C8E6E5.6000005@redhat.com \
--to=pbonzini@redhat.com \
--cc=javier.picorel@epfl.ch \
--cc=qemu-devel@nongnu.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 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).