forked from ~ljy/RK356X_SDK_RELEASE

blame | history | patch | commit | commitdiff
hc
2024-10-22 8ac6c7a54ed1b98d142dce24b11c6de6a1e239a5 
 kernel/Documentation/ABI/testing/sysfs-driver-pciback
....@@ -7,7 +7,22 @@
77                 the format of DDDD:BB:DD.F-REG:SIZE:MASK will allow the guest
88                 to write and read from the PCI device. That is Domain:Bus:
99                 Device.Function-Register:Size:Mask (Domain is optional).
10
-                For example:
11
-                #echo 00:19.0-E0:2:FF > /sys/bus/pci/drivers/pciback/quirks
10
+                For example::
11
+
12
+                  #echo 00:19.0-E0:2:FF > /sys/bus/pci/drivers/pciback/quirks
13
+
1214                 will allow the guest to read and write to the configuration
1315                 register 0x0E.
16
+
17
+What:           /sys/bus/pci/drivers/pciback/allow_interrupt_control
18
+Date:           Jan 2020
19
+KernelVersion:  5.6
20
+Contact:        xen-devel@lists.xenproject.org
21
+Description:
22
+                List of devices which can have interrupt control flag (INTx,
23
+                MSI, MSI-X) set by a connected guest. It is meant to be set
24
+                only when the guest is a stubdomain hosting device model (qemu)
25
+                and the actual device is assigned to a HVM. It is not safe
26
+                (similar to permissive attribute) to set for a devices assigned
27
+                to a PV guest. The device is automatically removed from this
28
+                list when the connected pcifront terminates.