On Mon, 2012-06-04 at 16:43 +1000, Michael Ellerman wrote:
There is some chance this will result in breakage because the driver
asks for N - and assumes that is what was allocated - and the device is
configured for > N.
We can fix that. We can whack the configuration back with N, just know
that we have "allocated" > N.
But that's a hypothetical, and we know the current approach sucks
because it will result in many drivers falling back to a single
interrupt.
I think this is the least-worst approach in light of the FW limitations,
and we can always add quirks in here if we really have to.
Paul is the pseries maintainer so he gets to ACK or NAK it, but from an
MSI point of view it gets my +1.
Cheers,
Ben.