do not use timedwait on qemu_halt_cond
commit9705fbb5636fbe36956e6886227e9e871689cf83
authorPaolo Bonzini <pbonzini@redhat.com>
Sat, 12 Mar 2011 16:44:00 +0000 (12 17:44 +0100)
committerBlue Swirl <blauwirbel@gmail.com>
Sun, 13 Mar 2011 14:44:22 +0000 (13 14:44 +0000)
tree1ed88bd7ff2299e8d855207d8347069ec99e1153
parent67bb172f9d995880a9c752e9f33819f4a63a3fda
do not use timedwait on qemu_halt_cond

The following conditions can cause cpu_has_work(env) to become true:

- env->queued_work_first: run_on_cpu is already kicking the VCPU

- env->stop = 1: pause_all_vcpus is already kicking the VCPU

- env->stopped = 0: resume_all_vcpus is already kicking the VCPU

- vm_running = 1: vm_start is calling resume_all_vcpus

- env->halted = 0: see previous patch

- qemu_cpu_has_work(env): when it becomes true, board code should set
  env->halted = 0 too.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
cpus.c