search for: zhanghy

...virtio-scsi, who still is waiting for msix. "Hence, the interrupt will not be acknowledged and the guest becomes flooded with IRQ 11 interrupt." Fortunately it's not a livelock for upstream, because of: commit 184564efae4d775225c8fe3b762a56956fb1f827 Author: Zhang Haoyu <zhanghy at sangfor.com> Date: Thu Sep 11 16:47:04 2014 +0800 kvm: ioapic: conditionally delay irq delivery duringeoi broadcast But we still should do the shutdown right. I also propose to not shutdown msix from pci core shutdown if the device doesn't have shutdown function: http://www....

...virtio-scsi, who still is waiting for msix. "Hence, the interrupt will not be acknowledged and the guest becomes flooded with IRQ 11 interrupt." Fortunately it's not a livelock for upstream, because of: commit 184564efae4d775225c8fe3b762a56956fb1f827 Author: Zhang Haoyu <zhanghy at sangfor.com> Date: Thu Sep 11 16:47:04 2014 +0800 kvm: ioapic: conditionally delay irq delivery duringeoi broadcast But we still should do the shutdown right. I also propose to not shutdown msix from pci core shutdown if the device doesn't have shutdown function: http://www....

On Wed, 03/11 10:06, Michael S. Tsirkin wrote: > On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote: > > Currently shutdown is nop for virtio devices, but the core code could > > remove things behind us such as MSI-X handler etc. For example in the > > case of virtio-scsi-pci, the device may still try to send interupts, > > which will be on IRQ lines seeing MSI-X

On Wed, 03/11 10:06, Michael S. Tsirkin wrote: > On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote: > > Currently shutdown is nop for virtio devices, but the core code could > > remove things behind us such as MSI-X handler etc. For example in the > > case of virtio-scsi-pci, the device may still try to send interupts, > > which will be on IRQ lines seeing MSI-X