From: Paolo Bonzini [mailto:pbonz...@redhat.com]
On 03/02/2015 11:51, Pavel Dovgaluk wrote:
From: Paolo Bonzini [mailto:pbonz...@redhat.com]
On 22/01/2015 09:52, Pavel Dovgalyuk wrote:
Clock ticks are considered as the sources of non-deterministic data for
virtual machine. This patch
On 03/02/2015 12:23, Pavel Dovgaluk wrote:
Only to the cpu_get_ticks usage. The others are okay.
cpu_get_ticks cannot call cpu_get_real_ticks in icount mode.
You're right, but...
And other functions can.
... which functions? cpu_enable_ticks and cpu_disable_ticks call it,
but the
From: Paolo Bonzini [mailto:pbonz...@redhat.com]
On 22/01/2015 09:52, Pavel Dovgalyuk wrote:
Clock ticks are considered as the sources of non-deterministic data for
virtual machine. This patch implements saving the clock values when they
are acquired (virtual, host clock, rdtsc, and some
On 03/02/2015 11:51, Pavel Dovgaluk wrote:
From: Paolo Bonzini [mailto:pbonz...@redhat.com]
On 22/01/2015 09:52, Pavel Dovgalyuk wrote:
Clock ticks are considered as the sources of non-deterministic data for
virtual machine. This patch implements saving the clock values when they
are
On 22/01/2015 09:52, Pavel Dovgalyuk wrote:
Clock ticks are considered as the sources of non-deterministic data for
virtual machine. This patch implements saving the clock values when they
are acquired (virtual, host clock, rdtsc, and some other timers).
When replaying the execution
Clock ticks are considered as the sources of non-deterministic data for
virtual machine. This patch implements saving the clock values when they
are acquired (virtual, host clock, rdtsc, and some other timers).
When replaying the execution corresponding values are read from log and
transfered to
