On Wed, 22 Jun 2011, Andreas F?rber wrote:
Am 21.06.2011 um 12:24 schrieb Nilay Vaish:
Is there a way to know how many cycles the virtual machine has been running
for?
No. QEMU's emulation is not cycle-accurate.
The instruction counter (icount) gives you an indication of how much workload
Am 21.06.2011 um 12:24 schrieb Nilay Vaish:
Is there a way to know how many cycles the virtual machine has been
running for?
No. QEMU's emulation is not cycle-accurate.
The instruction counter (icount) gives you an indication of how much
workload the guest has processed but no indication h
Nilay Vaish writes:
> I would like to determine the later. icount will give the instruction count. I
> need the instruction count as well, but is there some way to determine the
> guest
> cycles as well?
On the current implementation, the number of cycles is directly related
to the icount, so wh
On Tue, 21 Jun 2011, Llu??s wrote:
Nilay Vaish writes:
Let me ask a more pointed question. Is there a way to know how many
cycles the virtual machine has been running for? A comment that
appears before the defintion of the TimerState structure -- guest
cycle counter.
AFAIR, the TimerState ca
Nilay Vaish writes:
> Let me ask a more pointed question. Is there a way to know how many
> cycles the virtual machine has been running for? A comment that
> appears before the defintion of the TimerState structure -- guest
> cycle counter.
AFAIR, the TimerState captures the amount of host nsec/c
On Mon, 20 Jun 2011, Llu??s wrote:
Nilay writes:
I am trying to understand the structures that QEMU saves when do_savevm()
is invoked. Can anyone explain to me the fields that are part of the
TimerState structure in qemu-timer.c?
If my meory does not fail me, its main task is to capture wha
Nilay writes:
> I am trying to understand the structures that QEMU saves when do_savevm()
> is invoked. Can anyone explain to me the fields that are part of the
> TimerState structure in qemu-timer.c?
If my meory does not fail me, its main task is to capture what is the
time in the host whenever
Hi
I am trying to understand the structures that QEMU saves when do_savevm()
is invoked. Can anyone explain to me the fields that are part of the
TimerState structure in qemu-timer.c?
Thanks
Nilay
