Alex Williamson :
[...]
> > Oh right, I looked for code references to the register but didn't notice
> > that Linux configures it for MSI, not MSI-X. In my brief testing I only
> > saw that Windows generates interrupts on the first vector, so perhaps
> > not much lost without the extra vectors.
On Mon, 2014-05-12 at 14:28 -0600, Alex Williamson wrote:
> On Mon, 2014-05-12 at 22:02 +0200, Francois Romieu wrote:
> > Alex Williamson :
> > [...]
> > > device MSI will be blocked. The Linux driver doesn't make use of this
> > > window, so apparently it's not required to make use of MSI-X. Th
Alex Williamson :
[...]
> device MSI will be blocked. The Linux driver doesn't make use of this
> window, so apparently it's not required to make use of MSI-X. This
It does not really use MSI-X (no RSS).
> quirk makes the device work with the Windows driver that does use this
> window for MSI-
On Mon, 2014-05-12 at 22:02 +0200, Francois Romieu wrote:
> Alex Williamson :
> [...]
> > device MSI will be blocked. The Linux driver doesn't make use of this
> > window, so apparently it's not required to make use of MSI-X. This
>
> It does not really use MSI-X (no RSS).
Oh right, I looked f
This device is ridiculous. It has two MMIO BARs, BAR4 and BAR2. BAR4
hosts the MSI-X table, so oviously it would be too easy to access it
directly, instead it creates a window register in BAR2 that, among
other things, provides access to the MSI-X table. This means MSI-X
doesn't work in the gues
