| commit | 2ad9e9d19f5e3ef39d0b21987071fe6e98b5aa74 | |
| author | Jan Kiszka <jan.kiszka@siemens.com> | |
| Thu, 8 Sep 2011 10:51:35 +0000 (8 12:51 +0200) | ||
| committer | Marcelo Tosatti <mtosatti@redhat.com> | |
| Fri, 9 Sep 2011 17:05:26 +0000 (9 14:05 -0300) | ||
| tree | 709d4689234c2786eeec344c00f4725443650cf2 | treesnapshot (tar.gz zip) |
| parent | a676b1deef109b57b0a28a27fe67ff45f4a4aa1e | commitdiff |
qemu-kvm: pc: Do not start APIC timer spuriously
apic_timer_update not only calculates the next timer expiry that we need
to write out the vmstate, it may also start the timer of the user space
APIC model. That can cause spurious signals to the corresponding vCPU
thread when the timer expires. Fix this by using the new apic_next_timer
that does not start the timer.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
apic_timer_update not only calculates the next timer expiry that we need
to write out the vmstate, it may also start the timer of the user space
APIC model. That can cause spurious signals to the corresponding vCPU
thread when the timer expires. Fix this by using the new apic_next_timer
that does not start the timer.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
| hw/apic.c | diffblobblamehistory |