| commit | c6a94ba5f9b8240f90ac2bf5ae5249bf5590c438 | |
| author | Alexander Graf <agraf@suse.de> | |
| Tue, 9 Feb 2010 16:37:10 +0000 (9 17:37 +0100) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Sun, 14 Feb 2010 14:10:54 +0000 (14 16:10 +0200) | ||
| tree | 2074b1d48ab1d6c172abdd30f7a2bdb3c1a29433 | treesnapshot (tar.gz zip) |
| parent | b2eca4453fb60c85c63912b7218b41b521165d94 | commitdiff |
PPC: Add timer when running KVM
For some odd reason we sometimes hang inside KVM forever. I'd guess it's
a race condition where we actually have a level triggered interrupt, but
the infrastructure can't expose that yet, so the guest ACKs it, goes to
sleep and never gets notified that there's still an interrupt pending.
As a quick workaround, let's just wake up every 500 ms. That way we can
assure that we're always reinjecting interrupts in time.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
For some odd reason we sometimes hang inside KVM forever. I'd guess it's
a race condition where we actually have a level triggered interrupt, but
the infrastructure can't expose that yet, so the guest ACKs it, goes to
sleep and never gets notified that there's still an interrupt pending.
As a quick workaround, let's just wake up every 500 ms. That way we can
assure that we're always reinjecting interrupts in time.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
| target-ppc/kvm.c | diffblobblamehistory |