drivers/gpu/drm/xe/xe_sriov_vf_types.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_sriov_vf_types.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_sriov_vf_types.h- Extension
.h- Size
- 1010 bytes
- Lines
- 48
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.hlinux/workqueue_types.hxe_sriov_vf_ccs_types.h
Detected Declarations
struct xe_sriov_vf_relay_versionstruct xe_device_vf
Annotated Snippet
struct xe_sriov_vf_relay_version {
/** @major: major version. */
u16 major;
/** @minor: minor version. */
u16 minor;
};
/**
* struct xe_device_vf - Xe Virtual Function related data
*
* The data in this structure is valid only if driver is running in the
* @XE_SRIOV_MODE_VF mode.
*/
struct xe_device_vf {
/** @pf_version: negotiated VF/PF ABI version. */
struct xe_sriov_vf_relay_version pf_version;
/** @migration: VF Migration state data */
struct {
/**
* @migration.disabled: flag indicating if migration support
* was turned off due to missing prerequisites
*/
bool disabled;
} migration;
/** @ccs: VF CCS state data */
struct xe_sriov_vf_ccs ccs;
};
#endif
Annotation
- Immediate include surface: `linux/types.h`, `linux/workqueue_types.h`, `xe_sriov_vf_ccs_types.h`.
- Detected declarations: `struct xe_sriov_vf_relay_version`, `struct xe_device_vf`.
- 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.