Thanks Alex, Then, Is there any other ways to stop accidental unload of PF driver while still some VFs are accessing by the running VMs. Regards, Sreekanth On Wed, Aug 20, 2014 at 6:16 PM, Alex Williamson <alex.williamson@xxxxxxxxxx> wrote: > On Wed, 2014-08-20 at 16:39 +0530, Sreekanth Reddy wrote: >> HI, >> >> For SRIOV support, currently in the KVM environment, mpt3sas driver >> can use the API pci_vfs_assigned() to know the number of VFs that are >> currently assigned to the running VMs. So that during the PF driver >> unload time, if the return value of this API is greater than zero the >> our driver won't call the pci_disable_sriov() to disable the VFs. >> >> Now for the same purpose in XEN environment, is there any API similar >> to pci_vfs_assigned() which the low lever device driver can use to >> know 'the number of VFs that are currently assigned to the running >> VMs'. In XEN environment this API pci_vfs_assigned() will return >> always zero even though VFs are assigned to the running VMs. > > Note that pci_vfs_assigned() assigned is only used by legacy KVM device > assignment and primarily as a workaround for not using an actual > host-based device driver to manage device ownership. When using > VFIO-based device assignment with KVM, pci_vfs_assigned() is not > updated. Please don't rely on this interface. Thanks, > > Alex > -- 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
