On Wed, Apr 30, 2014 at 05:49:33PM -0600, Bjorn Helgaas wrote: > I mistakenly assumed this would have to wait because I thought there were > other pci_enable_msi_block() users that wouldn't be removed until the v3.16 > merge window. But I think I was wrong: I put your GenWQE patch in my tree, > and I think that was the last use, so I can just add this patch on top. That is right, GenWQE is the last one. > But I need a little help understanding the changelog: > > > Up until now, when enabling MSI mode for a device a single > > successful call to arch_msi_check_device() was followed by > > a single call to arch_setup_msi_irqs() function. > > I understand this part; the following two paths call > arch_msi_check_device() once and then arch_setup_msi_irqs() once: > > pci_enable_msi_block > pci_msi_check_device > arch_msi_check_device > msi_capability_init > arch_setup_msi_irqs > > pci_enable_msix > pci_msi_check_device > arch_msi_check_device > msix_capability_init > arch_setup_msi_irqs > > > Yet, if arch_msi_check_device() returned success we should be > > able to call arch_setup_msi_irqs() multiple times - while it > > returns a number of MSI vectors that could have been allocated > > (a third state). > > I don't know what you mean by "a third state." That is "a number of MSI vectors that could have been allocated", which is neither success nor failure. In previous conversations someone branded it this as "third state". > Previously we only called arch_msi_check_device() once. After your patch, > pci_enable_msi_range() can call it several times. The only non-trivial > implementation of arch_msi_check_device() is in powerpc, and all the > ppc_md.msi_check_device() possibilities look safe to call multiple times. Yep, I see it the same way. > After your patch, the pci_enable_msi_range() path can also call > arch_setup_msi_irqs() several times. I don't see a problem with that -- > even if the first call succeeds and allocates something, then a subsequent > call fails, I assume the allocations will be cleaned up when > msi_capability_init() calls free_msi_irqs(). Well, the potential problem related to the fact arch_msi_check_device() could be called with 'nvec1' while arch_setup_msi_irqs() could be called with 'nvec2', where 'nvec1' > 'nvec2'. While it is not a problem with current implementations, in therory it is possible free_msi_irqs() could be called with 'nvec2' and fail to clean up 'nvec1' - 'nvec2' number of resources. The only assumption that makes the above scenario impossible is if arch_msi_check_device() is stateless. Again, that is purely theoretical with no particular architecture in mind. > > This update makes use of the assumption described above. It > > could have broke things had the architectures done any pre- > > allocations or switch to some state in a call to function > > arch_msi_check_device(). But because arch_msi_check_device() > > is expected stateless and MSI resources are allocated in a > > follow-up call to arch_setup_msi_irqs() we should be fine. > > I guess you mean that your patch assumes arch_msi_check_device() is > stateless. That looks like a safe assumption to me. Moreover, if arch_msi_check_device() was not stateless then it would be superfluous, since all state switches and allocations are done in arch_setup_msi_irqs() anyway. In fact, I think arch_msi_check_device() could be eliminated, but I do not want to engage with PPC folks at this stage ;) > arch_setup_msi_irqs() is clearly not stateless, but I assume > free_msi_irqs() is enough to clean up any state if we fail. > > Bjorn -- Regards, Alexander Gordeev agordeev@xxxxxxxxxx
