On Thursday 18 April 2013 11:48, Michael S. Tsirkin wrote: > On Thu, Apr 18, 2013 at 12:40:09PM +0300, Jack Morgenstein wrote: > > On Thursday 18 April 2013 11:33, Michael S. Tsirkin wrote: > > > But for pci_sriov_enable, the situation is actually very simple: > > > VFs almost never use the same driver as the PF so the warning > > > is bogus there. > > > > > What about the case where the VF driver IS the same as the PF driver? > > Then it can deadlock, e.g. if driver takes a global mutex. But it's an > internal driver issue the, you can trigger a deadlock through hardware > too, e.g. if VF initialization blocks until PF is fully initialized. > I think it's not the case for Mellanox, is it? Correct, the Mellanox driver does not deadlock. > This is what I refer to: would be nice to fix nested probing in general > but it seems disabling the warning is the best we can do for 3.9 since > it causes false positives. > > -- 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
