cachepc-linux

Fork of AMDESE/linux with modifications for CachePC side-channel attack
git clone https://git.sinitax.com/sinitax/cachepc-linux
Log | Files | Refs | README | LICENSE | sfeed.txt

sysfs-bus-vdpa (2328B)


      1What:		/sys/bus/vdpa/driver_autoprobe
      2Date:		March 2020
      3Contact:	virtualization@lists.linux-foundation.org
      4Description:
      5		This file determines whether new devices are immediately bound
      6		to a driver after the creation. It initially contains 1, which
      7		means the kernel automatically binds devices to a compatible
      8		driver immediately after they are created.
      9
     10		Writing "0" to this file disable this feature, any other string
     11		enable it.
     12
     13What:		/sys/bus/vdpa/driver_probe
     14Date:		March 2020
     15Contact:	virtualization@lists.linux-foundation.org
     16Description:
     17		Writing a device name to this file will cause the kernel binds
     18		devices to a compatible driver.
     19
     20		This can be useful when /sys/bus/vdpa/driver_autoprobe is
     21		disabled.
     22
     23What:		/sys/bus/vdpa/drivers/.../bind
     24Date:		March 2020
     25Contact:	virtualization@lists.linux-foundation.org
     26Description:
     27		Writing a device name to this file will cause the driver to
     28		attempt to bind to the device. This is useful for overriding
     29		default bindings.
     30
     31What:		/sys/bus/vdpa/drivers/.../unbind
     32Date:		March 2020
     33Contact:	virtualization@lists.linux-foundation.org
     34Description:
     35		Writing a device name to this file will cause the driver to
     36		attempt to unbind from the device. This may be useful when
     37		overriding default bindings.
     38
     39What:		/sys/bus/vdpa/devices/.../driver_override
     40Date:		November 2021
     41Contact:	virtualization@lists.linux-foundation.org
     42Description:
     43		This file allows the driver for a device to be specified.
     44		When specified, only a driver with a name matching the value
     45		written to driver_override will have an opportunity to bind to
     46		the device. The override is specified by writing a string to the
     47		driver_override file (echo vhost-vdpa > driver_override) and may
     48		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 the
     51		device from its current driver or make any attempt to
     52		automatically load the specified driver. If no driver with a
     53		matching name is currently loaded in the kernel, the device will
     54		not bind to any driver. This also allows devices to opt-out of
     55		driver binding using a driver_override name such as "none".
     56		Only a single driver may be specified in the override, there is
     57		no support for parsing delimiters.