Skip to content
  • Paolo Bonzini's avatar
    enable vm_clock to "warp" in the iothread+icount case · ab33fcda
    Paolo Bonzini authored
    
    
    The previous patch however is not enough, because if the virtual CPU
    goes to sleep waiting for a future timer interrupt to wake it up, qemu
    deadlocks.  The timer interrupt never comes because time is driven by
    icount, but the vCPU doesn't run any insns.
    
    You could say that VCPUs should never go to sleep in icount
    mode if there is a pending vm_clock timer; rather time should
    just warp to the next vm_clock event with no sleep ever taking place.
    Even better, you can sleep for some time related to the
    time left until the next event, to avoid that the warps are too visible
    externally; for example, you could be sending network packets continously
    instead of every 100ms.
    
    This is what this patch implements.  qemu_clock_warp is called: 1)
    whenever a vm_clock timer is adjusted, to ensure the warp_timer is
    synchronized; 2) at strategic points in the CPU thread, to make sure
    the insn counter is synchronized before the CPU starts running.
    In any case, the warp_timer is disabled while the CPU is running,
    because the insn counter will then be making progress on its own.
    
    Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
    Tested-by: default avatarEdgar E. Iglesias <edgar.iglesias@gmail.com>
    Signed-off-by: default avatarEdgar E. Iglesias <edgar.iglesias@gmail.com>
    ab33fcda