Marcelo Tosatti wrote:
I'm worried about:
- boot guest using local apic timer
- reset
- boot with pit timer
- a zillion interrupts
So at the very least, we need a limiter.
Or have a new notifier on kvm_pic_reset, instead of simply acking one
pending irq? That seems the appropriate
Avi Kivity wrote:
Marcelo Tosatti wrote:
I'm worried about:
- boot guest using local apic timer
- reset
- boot with pit timer
- a zillion interrupts
So at the very least, we need a limiter.
Or have a new notifier on kvm_pic_reset, instead of simply acking one
pending irq? That seems
On Sun, Jan 04, 2009 at 06:14:45PM +0200, Avi Kivity wrote:
While the PIT is masked the guest cannot ack the irq, so the reinject logic
will never allow the interrupt to be injected.
Fix by resetting the reinjection counters on unmask.
Unbreaks Xen.
Signed-off-by: Avi Kivity
Marcelo Tosatti wrote:
On Sun, Jan 04, 2009 at 06:14:45PM +0200, Avi Kivity wrote:
While the PIT is masked the guest cannot ack the irq, so the reinject logic
will never allow the interrupt to be injected.
Fix by resetting the reinjection counters on unmask.
Unbreaks Xen.
diff --git
On Mon, Jan 05, 2009 at 10:59:01PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
On Sun, Jan 04, 2009 at 06:14:45PM +0200, Avi Kivity wrote:
While the PIT is masked the guest cannot ack the irq, so the reinject logic
will never allow the interrupt to be injected.
Fix by resetting the
While the PIT is masked the guest cannot ack the irq, so the reinject logic
will never allow the interrupt to be injected.
Fix by resetting the reinjection counters on unmask.
Unbreaks Xen.
Signed-off-by: Avi Kivity a...@redhat.com
---
arch/x86/kvm/i8254.c | 15 +++
