diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2011-02-03 14:49:00 +0100 |
|---|---|---|
| committer | Anthony Liguori <aliguori@us.ibm.com> | 2011-02-04 06:33:26 -0600 |
| commit | 6ad0a1ed21ecd187dbe3239eb45c3598672af6a8 (patch) | |
| tree | 26cee8f2413348788f943b53ac98257ce3675391 /block | |
| parent | 9c13246ac13a87e05b5e6e7158e715dfa65fc7aa (diff) | |
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>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions