On 01/05/19 01:01, Alex Williamson wrote: > Poking at this a bit, we can add kvm_irqchip_is_split() to the set of > things we test for in hw/vfio/pci.c:vfio_intx_enable_kvm() to avoid the > KVM INTx bypass when using split IRQ chip.
Yes, this should be enough. > The only way I can get the GPU/Windows configuration usable is to > assert the IRQ, immediately de-assert, and unmask the device all from > vfio_intx_interrupt(). An interrupt intensive graphics benchmark runs > at ~80% of KVM irqchip with about 10% more CPU load with this > experiment (but it actually runs!). Nice. If you can do it directly from hw/vfio there may be no need to do more changes to the IOAPIC, and least not immediately. But that is not a good emulation of INTX, isn't it? IIUC, it relies on the level-triggered interrupt never being masked in the IOAPIC. > Any other insights appreciated, and I really would like to understand > what we've gained with split irqchip and whether it's worth this. We've gained guest interrupt remapping support, we are not relying on newer kernel versions, and the attack surface from the guest to the hypervisor is smaller. Paolo
