drivers/gpu/drm/xe/xe_sriov_pf_service_types.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_sriov_pf_service_types.h

Extension

.h

Size

893 bytes

Lines

37

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.h

Detected Declarations

• struct xe_sriov_pf_service_version
• struct xe_sriov_pf_service

Annotated Snippet

struct xe_sriov_pf_service_version {
	u16 major;
	u16 minor;
};

/**
 * struct xe_sriov_pf_service - Data used by the PF service.
 * @version: information about VF/PF ABI versions for current platform.
 * @version.base: lowest VF/PF ABI version that could be negotiated with VF.
 * @version.latest: latest VF/PF ABI version supported by the PF driver.
 */
struct xe_sriov_pf_service {
	struct {
		struct xe_sriov_pf_service_version base;
		struct xe_sriov_pf_service_version latest;
	} version;
};

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct xe_sriov_pf_service_version`, `struct xe_sriov_pf_service`.
• 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.