> I think this is the issue:
>
> I/O threadvCPU thread
> ---
>executes 1,000,000,000-th instruction
>wakes up I/O thread
> find
On 12/01/2018 19:03, Steven Seeger wrote:
>> That's probably because the CPU runs in the background while the timers
>> run. So QEMU_CLOCK_VIRTUAL is _not_ latched while the timers run.
>> Would that explain it?
>
> Yes that would explain it. QEMU_CLOCK_VIRTUAL should increase with number of
> e
On Friday, January 12, 2018 12:19:22 PM EST Paolo Bonzini wrote:
>
> Correct. I mentioned it because you also had "-icount sleep=off" in
> your previous message.
Yes I have tried both. With sleep=off, I get the faster interrupt response
(better granularity) but with sleep=on, it is poor. Again,
On 12/01/2018 18:12, Steven Seeger wrote:
> On Friday, January 12, 2018 11:52:57 AM EST Paolo Bonzini wrote:
>> What is the guest doing in the meanwhile?
>
> The guest is running vxWorks with several threads. The CPU does idle at
> times.
>
>> virtual time increases only when instructions are e
On Friday, January 12, 2018 11:52:57 AM EST Paolo Bonzini wrote:
> What is the guest doing in the meanwhile?
The guest is running vxWorks with several threads. The CPU does idle at times.
> virtual time increases only when instructions are executed, or when the
> CPUs are idle (in the latter cas
On 12/01/2018 17:19, Steven Seeger wrote:
> A good example of this would be that say I have an interrupt that occurs
> every
> second. If I were to print out the virtual time that interrupt occurs in the
> device model, I should see a time of:
>
> 1.00
> 2.00
> 3.00
> 4.00
>
>
Hi guys. I'm the poster on the qemu-discuss list about some technical icount
questions and was told to come over here to qemu-devel.
My scenario: x86-64 host running qemu/ppc-softmmu with an unmodfied ppc750 cpu
and a custom board target with chipset I implemented.
I am trying to use icount to