Documentation/ABI/testing/sysfs-driver-pciback

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-driver-pciback

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-driver-pciback
Extension: [no extension]
Size: 1378 bytes
Lines: 29
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Touches IRQ or DMA behavior; this matters for the representative real-device path.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

What:           /sys/bus/pci/drivers/pciback/quirks
Date:           Oct 2011
KernelVersion:  3.1
Contact:        xen-devel@lists.xenproject.org
Description:
                If the permissive attribute is set, then writing a string in
                the format of DDDD:BB:DD.F-REG:SIZE:MASK will allow the guest
                to write and read from the PCI device. That is Domain:Bus:
                Device.Function-Register:Size:Mask (Domain is optional).
                For example::

                  #echo 00:19.0-E0:2:FF > /sys/bus/pci/drivers/pciback/quirks

                will allow the guest to read and write to the configuration
                register 0x0E.

What:           /sys/bus/pci/drivers/pciback/allow_interrupt_control
Date:           Jan 2020
KernelVersion:  5.6
Contact:        xen-devel@lists.xenproject.org
Description:
                List of devices which can have interrupt control flag (INTx,
                MSI, MSI-X) set by a connected guest. It is meant to be set
                only when the guest is a stubdomain hosting device model (qemu)
                and the actual device is assigned to a HVM. It is not safe
                (similar to permissive attribute) to set for a devices assigned
                to a PV guest. The device is automatically removed from this
                list when the connected pcifront terminates.

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.
IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.