tree 26cee8f2413348788f943b53ac98257ce3675391
parent 9c13246ac13a87e05b5e6e7158e715dfa65fc7aa
author Paolo Bonzini <pbonzini@redhat.com> 1296740940 +0100
committer Anthony Liguori <aliguori@us.ibm.com> 1296822806 -0600

Correct alarm deadline computation

When the QEMU_CLOCK_HOST clock was added, computation of its
deadline was added to qemu_next_deadline, which is correct but
incomplete.

I noticed this by reading the very convoluted rules whereby
qemu_next_deadline_dyntick is computed, which miss QEMU_CLOCK_HOST
when use_icount is true.  This patch inlines qemu_next_deadline
into qemu_next_deadline_dyntick, and then corrects the logic to skip
only QEMU_CLOCK_VIRTUAL when use_icount is true.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>