From: Paolo Bonzini <pbonzini@redhat.com>
To: andrzej zaborowski <balrogg@gmail.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/4] arm: switch real-time clocks to rtc_clock
Date: Fri, 17 Feb 2012 09:05:27 +0100 [thread overview]
Message-ID: <4F3E0A47.10001@redhat.com> (raw)
In-Reply-To: <CAOq732JfDJt2Ww7-NYHFVytO7atDG1yjkOcCkr4dfvkFVRjaSw@mail.gmail.com>
On 02/17/2012 08:09 AM, andrzej zaborowski wrote:
>> > This lets the user specify the desired semantics. By default, the RTC
>> > will follow adjustments from the host's NTP client. "-rtc clock=vm" will
>> > improve determinism with both icount and qtest. Finally, the previous
>> > behavior is available with "-rtc clock=rt".
> Generally this makes sense except for the omap1 "lpg" module where the
> clock state is not visible to the guest, only to the host. It
> emulates a blinking led.
Ok, then I think it's better to switch that one to vm_clock (so that you
could use it as a deterministic debugging aid with -icount, for
example). What do you think?
Paolo
next prev parent reply other threads:[~2012-02-17 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 12:06 [Qemu-devel] [PATCH 0/4] Use rtc_clock uniformly for ARM Paolo Bonzini
2012-01-20 12:06 ` [Qemu-devel] [PATCH 1/4] rtc: add -rtc clock=rt Paolo Bonzini
2012-01-20 12:06 ` [Qemu-devel] [PATCH 2/4] arm: switch real-time clocks to rtc_clock Paolo Bonzini
2012-02-17 7:09 ` andrzej zaborowski
2012-02-17 8:05 ` Paolo Bonzini [this message]
2012-02-17 8:24 ` andrzej zaborowski
2012-02-17 8:31 ` Paolo Bonzini
2012-01-20 12:06 ` [Qemu-devel] [PATCH 3/4] pl031: rearm alarm timer upon load Paolo Bonzini
2012-01-20 12:06 ` [Qemu-devel] [PATCH 4/4] pl031: switch clock base to rtc_clock Paolo Bonzini
2012-01-30 16:54 ` Peter Maydell
2012-01-30 17:02 ` Paolo Bonzini
2012-01-30 16:42 ` [Qemu-devel] [PATCH 0/4] Use rtc_clock uniformly for ARM Paolo Bonzini
2012-01-30 17:21 ` Peter Maydell
2012-01-31 7:28 ` 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=4F3E0A47.10001@redhat.com \
--to=pbonzini@redhat.com \
--cc=balrogg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.