On 02/17/2012 09:24 AM, andrzej zaborowski wrote:
>> > 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?
> I was thinking about potential visual effects.
vm_clock is the s
On 17 February 2012 09:05, Paolo Bonzini wrote:
> 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 icoun
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 a
On 20 January 2012 13:06, Paolo Bonzini 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
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".
Signed-off-by: Paolo Bonzini
---
hw/
