0001 What: /sys/bus/vdpa/driver_autoprobe
0002 Date: March 2020
0003 Contact: virtualization@lists.linux-foundation.org
0004 Description:
0005 This file determines whether new devices are immediately bound
0006 to a driver after the creation. It initially contains 1, which
0007 means the kernel automatically binds devices to a compatible
0008 driver immediately after they are created.
0009
0010 Writing "0" to this file disable this feature, any other string
0011 enable it.
0012
0013 What: /sys/bus/vdpa/driver_probe
0014 Date: March 2020
0015 Contact: virtualization@lists.linux-foundation.org
0016 Description:
0017 Writing a device name to this file will cause the kernel binds
0018 devices to a compatible driver.
0019
0020 This can be useful when /sys/bus/vdpa/driver_autoprobe is
0021 disabled.
0022
0023 What: /sys/bus/vdpa/drivers/.../bind
0024 Date: March 2020
0025 Contact: virtualization@lists.linux-foundation.org
0026 Description:
0027 Writing a device name to this file will cause the driver to
0028 attempt to bind to the device. This is useful for overriding
0029 default bindings.
0030
0031 What: /sys/bus/vdpa/drivers/.../unbind
0032 Date: March 2020
0033 Contact: virtualization@lists.linux-foundation.org
0034 Description:
0035 Writing a device name to this file will cause the driver to
0036 attempt to unbind from the device. This may be useful when
0037 overriding default bindings.
0038
0039 What: /sys/bus/vdpa/devices/.../driver_override
0040 Date: November 2021
0041 Contact: virtualization@lists.linux-foundation.org
0042 Description:
0043 This file allows the driver for a device to be specified.
0044 When specified, only a driver with a name matching the value
0045 written to driver_override will have an opportunity to bind to
0046 the device. The override is specified by writing a string to the
0047 driver_override file (echo vhost-vdpa > driver_override) and may
0048 be cleared with an empty string (echo > driver_override).
0049 This returns the device to standard matching rules binding.
0050 Writing to driver_override does not automatically unbind the
0051 device from its current driver or make any attempt to
0052 automatically load the specified driver. If no driver with a
0053 matching name is currently loaded in the kernel, the device will
0054 not bind to any driver. This also allows devices to opt-out of
0055 driver binding using a driver_override name such as "none".
0056 Only a single driver may be specified in the override, there is
0057 no support for parsing delimiters.
