Documentation/ABI/testing/sysfs-driver-intel-xe-sriov
Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-driver-intel-xe-sriov
File Facts
- System
- Linux kernel
- Corpus path
Documentation/ABI/testing/sysfs-driver-intel-xe-sriov- Extension
[no extension]- Size
- 7594 bytes
- Lines
- 191
- 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.
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/xe/.../sriov_admin/
Date: October 2025
KernelVersion: 6.19
Contact: intel-xe@lists.freedesktop.org
Description:
This directory appears for the particular Intel Xe device when:
- device supports SR-IOV, and
- device is a Physical Function (PF), and
- driver support for the SR-IOV PF is enabled on given device.
This directory is used as a root for all attributes required to
manage both Physical Function (PF) and Virtual Functions (VFs).
What: /sys/bus/pci/drivers/xe/.../sriov_admin/pf/
Date: October 2025
KernelVersion: 6.19
Contact: intel-xe@lists.freedesktop.org
Description:
This directory holds attributes related to the SR-IOV Physical
Function (PF).
What: /sys/bus/pci/drivers/xe/.../sriov_admin/vf1/
What: /sys/bus/pci/drivers/xe/.../sriov_admin/vf2/
What: /sys/bus/pci/drivers/xe/.../sriov_admin/vf<N>/
Date: October 2025
KernelVersion: 6.19
Contact: intel-xe@lists.freedesktop.org
Description:
These directories hold attributes related to the SR-IOV Virtual
Functions (VFs).
Note that the VF number <N> is 1-based as described in PCI SR-IOV
specification as the Xe driver follows that naming schema.
There could be "vf1", "vf2" and so on, up to "vf<N>", where <N>
matches the value of the "sriov_totalvfs" attribute.
What: /sys/bus/pci/drivers/xe/.../sriov_admin/pf/profile/exec_quantum_ms
What: /sys/bus/pci/drivers/xe/.../sriov_admin/pf/profile/preempt_timeout_us
What: /sys/bus/pci/drivers/xe/.../sriov_admin/pf/profile/sched_priority
What: /sys/bus/pci/drivers/xe/.../sriov_admin/vf<n>/profile/exec_quantum_ms
What: /sys/bus/pci/drivers/xe/.../sriov_admin/vf<n>/profile/preempt_timeout_us
What: /sys/bus/pci/drivers/xe/.../sriov_admin/vf<n>/profile/sched_priority
Date: October 2025
KernelVersion: 6.19
Contact: intel-xe@lists.freedesktop.org
Description:
These files expose scheduling parameters for the PF and its VFs, and
are visible only on Intel Xe platforms that use time-sliced GPU sharing.
They can be changed even if VFs are enabled and running and reflect the
settings of all tiles/GTs assigned to the given function.
exec_quantum_ms: (RW) unsigned integer
The GT execution quantum (EQ) in [ms] for the given function.
Actual quantum value might be aligned per HW/FW requirements.
Default is 0 (unlimited).
preempt_timeout_us: (RW) unsigned integer
The GT preemption timeout in [us] of the given function.
Actual timeout value might be aligned per HW/FW requirements.
Default is 0 (unlimited).
sched_priority: (RW/RO) string
The GT scheduling priority of the given function.
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
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.