> It's possible that the device can do MSI(X), but that using MSI(X) > requires other platform resources (e.g. interrupt source numbers) and > there are none free. I believe the platform guarantees a minimum > number of MSI(X) interrupts per function, but a pci_enable_msix() call > may not be able to give the driver as many MSI-X interrupts as it is > requesting even if the function can handle that many.
However, the ibm,req#msi(-x) properties contain the number as requested by the device, and thus I expect them to be identical to the config space value. So if you are confident enough that our HV won't play any tricks there in the future, reading the config space is as good as hooking that check() callback, though it might not be vs. some other HV for some other platform that might be more strict. We cannot know in advance how much max the HV will give us without actually trying ibm,change-msi and see the result code for it unfortunately. Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/