On 11/07/16 03:32, Bharat Kumar Gogada wrote: > Hi, > > I have a query. > I see that when we use PCI_MSI_IRQ_DOMAIN to handle MSI's, MSI address is not being > written in to end point's PCI_MSI_ADDRESS_LO/HI at the call pci_enable_msi_range. > > Instead it is being written at the time end point requests irq. > > Can any one tell the reason why is it handled in this manner ? Because there is no real need to do it earlier, and in some case you cannot allocate MSIs at that stage. pci_enable_msi_range only works out how many vectors are required. At least one MSI controller (GICv3 ITS) needs to know how many vectors are required before they can be provided to the end-point. Do you see any issue with this? Thanks, M. -- Jazz is not dead. It just smells funny... -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
