Merge tag 'pci-v4.12-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaa...

[GitHub/LineageOS/android_kernel_motorola_exynos9610.git] / Documentation / ABI / testing / sysfs-bus-pci

diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci
index e4e90104d7c38ff89bae718df7485337ee3e9108..44d4b2be92fd4a56ab2420944f76669a2466a304 100644 (file)
--- a/Documentation/ABI/testing/sysfs-bus-pci
+++ b/Documentation/ABI/testing/sysfs-bus-pci
@@ -301,3 +301,25 @@ Contact:   Emil Velikov <emil.l.velikov@gmail.com>
 Description:
                This file contains the revision field of the PCI device.
                The value comes from device config space. The file is read only.
+
+What:          /sys/bus/pci/devices/.../sriov_drivers_autoprobe
+Date:          April 2017
+Contact:       Bodong Wang<bodong@mellanox.com>
+Description:
+               This file is associated with the PF of a device that
+               supports SR-IOV.  It determines whether newly-enabled VFs
+               are immediately bound to a driver.  It initially contains
+               1, which means the kernel automatically binds VFs to a
+               compatible driver immediately after they are enabled.  If
+               an application writes 0 to the file before enabling VFs,
+               the kernel will not bind VFs to a driver.
+
+               A typical use case is to write 0 to this file, then enable
+               VFs, then assign the newly-created VFs to virtual machines.
+               Note that changing this file does not affect already-
+               enabled VFs.  In this scenario, the user must first disable
+               the VFs, write 0 to sriov_drivers_autoprobe, then re-enable
+               the VFs.
+
+               This is similar to /sys/bus/pci/drivers_autoprobe, but
+               affects only the VFs associated with a specific PF.