From: Steven Seeger <steven.seeger@flightsystems.net>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] deterministic qemu
Date: Wed, 31 Jan 2018 00:50:57 -0500 [thread overview]
Message-ID: <1811748.Ax3oce7GDK@wirbelwind> (raw)
I wanted to update the list on my progress and a follow-up of the "ppc and
icount" thread.
The issue I was seeing is the case where an io memory write triggers a timer
value to be set. In single-thread TCG, timers are run in
handle_icount_deadline() and once that's done, TBs are executed. Since cpu-
>icount_budget is 5000000 (icount==3), a timer being set to 88 microseconds
will fire way late. This caused the tremendous slowdown I was seeing during
the start of my binary when the vxWorks bootup banner came up. I have a simple
fix for this (set cpu->exit_request=1 in qemu_start_warp_timer, a total hack)
but I'm sure that's not "correct."
The other thing is -icount 3,align=on makes it run correctly assuming the host
can keep up.
The end result is every time I run my executable I get the same virtual clock
value for some given event. I'm very happy.
I still don't have a fix for the issue in commit
044897ef4a22af89aecb8df509477beba0a2e0ce but I reverted it and things are
working for me.
Steven
reply other threads:[~2018-01-31 5:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1811748.Ax3oce7GDK@wirbelwind \
--to=steven.seeger@flightsystems.net \
--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).