From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Andrzej Zaborowski <andrew.zaborowski@intel.com>
Subject: [Qemu-devel] direct usage of rt_clock instead of rtc_clock
Date: Wed, 18 Jan 2012 19:04:21 +0100 [thread overview]
Message-ID: <4F1709A5.5080201@redhat.com> (raw)
Hi Peter and Andrzej,
the following four files in hw/ are using rt_clock directly
omap1.c
pxa2xx.c
strongarm.c
twl92230.c
instead of rtc_clock. This means that they're not completely
deterministic when using -icount or in the future qtest. A simple
search-and-replace would be okay I think. However they could also use a
notifier to update the timers whenever the rtc_clock jumped backwards
(see commit 17604da). If you are going to add the notifier I'll happily
leave the work to you; otherwise I'll post the search-and-replace patch.
Paolo
next reply other threads:[~2012-01-18 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 18:04 Paolo Bonzini [this message]
2012-01-18 19:02 ` [Qemu-devel] direct usage of rt_clock instead of rtc_clock Peter Maydell
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=4F1709A5.5080201@redhat.com \
--to=pbonzini@redhat.com \
--cc=andrew.zaborowski@intel.com \
--cc=peter.maydell@linaro.org \
--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).