From: "Pavel Dovgalyuk" <dovgaluk@ispras.ru>
To: "'Paolo Bonzini'" <pbonzini@redhat.com>,
"'Alex Bennée'" <alex.bennee@linaro.org>
Cc: "'Nutaro, James J.'" <nutarojj@ornl.gov>,
mttcg@greensocs.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -rtc clock=vm with -icount 1, sleep=off introduces unexpected delays in device interactions
Date: Tue, 14 Mar 2017 15:18:22 +0300 [thread overview]
Message-ID: <000801d29cbd$12ab64a0$38022de0$@ru> (raw)
In-Reply-To: <be7ee11c-4c10-cee8-a35e-7905e0c44881@redhat.com>
> From: Paolo Bonzini [mailto:pbonzini@redhat.com]
> On 14/03/2017 13:10, Pavel Dovgalyuk wrote:
> > This is not the same.
> > BQL helped in making execution deterministic - no io and timer
> > callbacks were performed while CPU is executing.
> > Now iothread and CPU thread work simultaneously and timers can't
> > query virtual time correctly, because (if we could query number of executed
> > instructions) it may have different values on different runs.
> >
> > I guess you'll have to bring kicking CPU back on iothread invocation
> > to make execution deterministic in icount mode.
>
> Timers are fixed by my patch. I/O should also work if its effects are
> only apparent at given QEMU_CLOCK_VIRTUAL values.
Can you point me on that patch?
Pavel Dovgalyuk
next prev parent reply other threads:[~2017-03-14 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 19:38 [Qemu-devel] -rtc clock=vm with -icount 1, sleep=off introduces unexpected delays in device interactions Nutaro, James J.
2017-03-03 19:50 ` Frédéric Konrad
2017-03-06 13:08 ` Alex Bennée
2017-03-07 7:03 ` Pavel Dovgalyuk
2017-03-13 13:21 ` Alex Bennée
2017-03-14 12:10 ` Pavel Dovgalyuk
2017-03-14 12:15 ` Paolo Bonzini
2017-03-14 12:18 ` Pavel Dovgalyuk [this message]
2017-03-14 16:52 ` Paolo Bonzini
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='000801d29cbd$12ab64a0$38022de0$@ru' \
--to=dovgaluk@ispras.ru \
--cc=alex.bennee@linaro.org \
--cc=mttcg@greensocs.com \
--cc=nutarojj@ornl.gov \
--cc=pbonzini@redhat.com \
--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).