drivers/gpu/drm/xe/xe_sriov_types.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_sriov_types.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_sriov_types.h- Extension
.h- Size
- 998 bytes
- Lines
- 41
- Domain
- Driver Families
- Bucket
- drivers/gpu
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
Dependency Surface
linux/build_bug.h
Detected Declarations
enum xe_sriov_mode
Annotated Snippet
#ifndef _XE_SRIOV_TYPES_H_
#define _XE_SRIOV_TYPES_H_
#include <linux/build_bug.h>
/**
* VFID - Virtual Function Identifier
* @n: VF number
*
* Helper macro to represent Virtual Function (VF) Identifier.
* VFID(0) is used as alias to the PFID that represents Physical Function.
*
* Note: According to PCI spec, SR-IOV VF's numbers are 1-based (VF1, VF2, ...).
*/
#define VFID(n) (n)
#define PFID VFID(0)
/**
* enum xe_sriov_mode - SR-IOV mode
* @XE_SRIOV_MODE_NONE: bare-metal mode (non-virtualized)
* @XE_SRIOV_MODE_PF: SR-IOV Physical Function (PF) mode
* @XE_SRIOV_MODE_VF: SR-IOV Virtual Function (VF) mode
*/
enum xe_sriov_mode {
/*
* Note: We don't use default enum value 0 to allow catch any too early
* attempt of checking the SR-IOV mode prior to the actual mode probe.
*/
XE_SRIOV_MODE_NONE = 1,
XE_SRIOV_MODE_PF,
XE_SRIOV_MODE_VF,
};
static_assert(XE_SRIOV_MODE_NONE);
#endif
Annotation
- Immediate include surface: `linux/build_bug.h`.
- Detected declarations: `enum xe_sriov_mode`.
- Atlas domain: Driver Families / drivers/gpu.
- Implementation status: source implementation candidate.
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.