58 lines · plain
1What: /sys/bus/vdpa/drivers_autoprobe2Date: March 20203Contact: virtualization@lists.linux.dev4Description:5 This file determines whether new devices are immediately bound6 to a driver after the creation. It initially contains 1, which7 means the kernel automatically binds devices to a compatible8 driver immediately after they are created.9 10 Writing "0" to this file disable this feature, any other string11 enable it.12 13What: /sys/bus/vdpa/driver_probe14Date: March 202015Contact: virtualization@lists.linux.dev16Description:17 Writing a device name to this file will cause the kernel binds18 devices to a compatible driver.19 20 This can be useful when /sys/bus/vdpa/drivers_autoprobe is21 disabled.22 23What: /sys/bus/vdpa/drivers/.../bind24Date: March 202025Contact: virtualization@lists.linux.dev26Description:27 Writing a device name to this file will cause the driver to28 attempt to bind to the device. This is useful for overriding29 default bindings.30 31What: /sys/bus/vdpa/drivers/.../unbind32Date: March 202033Contact: virtualization@lists.linux.dev34Description:35 Writing a device name to this file will cause the driver to36 attempt to unbind from the device. This may be useful when37 overriding default bindings.38 39What: /sys/bus/vdpa/devices/.../driver_override40Date: November 202141Contact: virtualization@lists.linux.dev42Description:43 This file allows the driver for a device to be specified.44 When specified, only a driver with a name matching the value45 written to driver_override will have an opportunity to bind to46 the device. The override is specified by writing a string to the47 driver_override file (echo vhost-vdpa > driver_override) and may48 be cleared with an empty string (echo > driver_override).49 This returns the device to standard matching rules binding.50 Writing to driver_override does not automatically unbind the51 device from its current driver or make any attempt to52 automatically load the specified driver. If no driver with a53 matching name is currently loaded in the kernel, the device will54 not bind to any driver. This also allows devices to opt-out of55 driver binding using a driver_override name such as "none".56 Only a single driver may be specified in the override, there is57 no support for parsing delimiters.58