RE: Regression after "Remove support for reporting coalesced APIC IRQs"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Gleb Natapov [mailto:gleb@xxxxxxxxxx]
> Sent: Thursday, June 06, 2013 4:54 PM
> To: Jan Kiszka
> Cc: kvm@xxxxxxxxxxxxxxx; Ren, Yongjie
> Subject: Regression after "Remove support for reporting coalesced APIC
> IRQs"
> 
> Hi Jan,
> 
> I bisected [1] to f1ed0450a5fac7067590317cbf027f566b6ccbca.
>
Right. Before Gleb's mail, I also just did the bisection for this bug. 
The first bad commit is Jan's f1ed0450.

> Fortunately
> further investigation showed that it is not really related to removing
> APIC timer interrupt reinjection and the real problem is that we cannot
> assume that __apic_accept_irq() always injects interrupts like the patch
> does because the function skips interrupt injection if APIC is disabled.
> This misreporting screws RTC interrupt tracking, so further RTC interrupt
> are stopped to be injected. The simplest solution that I see is to revert
> most of the commit and only leave APIC timer interrupt reinjection.
> 
> If you have more elegant solution let me know.
> 
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=58931
> --
> 			Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux