Re: [Qemu-devel] [PATCH v2 22/42] ivshmem: Leave INTx alone when using MSI-X

2016-03-09 Thread Markus Armbruster
Marc-André Lureau writes: > Hi > > On Mon, Mar 7, 2016 at 8:25 PM, Markus Armbruster wrote: >> The ivshmem device can either use MSI-X or legacy INTx for interrupts. >> >> With MSI-X enabled, peer interrupt events trigger an MSI as they >> should. But software can still raise INTx via interrupt

Re: [Qemu-devel] [PATCH v2 22/42] ivshmem: Leave INTx alone when using MSI-X

2016-03-09 Thread Marc-André Lureau
Hi On Mon, Mar 7, 2016 at 8:25 PM, Markus Armbruster wrote: > The ivshmem device can either use MSI-X or legacy INTx for interrupts. > > With MSI-X enabled, peer interrupt events trigger an MSI as they > should. But software can still raise INTx via interrupt status and > mask register in BAR 0.

[Qemu-devel] [PATCH v2 22/42] ivshmem: Leave INTx alone when using MSI-X

2016-03-07 Thread Markus Armbruster
The ivshmem device can either use MSI-X or legacy INTx for interrupts. With MSI-X enabled, peer interrupt events trigger an MSI as they should. But software can still raise INTx via interrupt status and mask register in BAR 0. This is explicitly prohibited by PCI Local Bus Specification Revision