drivers/gpu/drm/xe/xe_survivability_mode_types.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_survivability_mode_types.h

Extension

.h

Size

1109 bytes

Lines

56

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/limits.h
• linux/types.h

Detected Declarations

• struct xe_survivability
• enum scratch_reg
• enum xe_survivability_type

Annotated Snippet

struct xe_survivability {
	/** @info: survivability debug info */
	u32 info[MAX_SCRATCH_REG];

	/** @size: number of scratch registers */
	u32 size;

	/** @boot_status: indicates critical/non critical boot failure */
	u8 boot_status;

	/** @mode: boolean to indicate survivability mode */
	bool mode;

	/** @type: survivability type */
	enum xe_survivability_type type;

	/** @fdo_mode: indicates if FDO mode is enabled */
	bool fdo_mode;

	/** @version: breadcrumb version of survivability mode  */
	u8 version;
};

#endif /* _XE_SURVIVABILITY_MODE_TYPES_H_ */

Annotation

• Immediate include surface: `linux/limits.h`, `linux/types.h`.
• Detected declarations: `struct xe_survivability`, `enum scratch_reg`, `enum xe_survivability_type`.
• 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.