drivers/gpu/drm/xe/xe_drm_ras_types.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_drm_ras_types.h

Extension

.h

Size

949 bytes

Lines

49

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/atomic.h
• drm/xe_drm.h

Detected Declarations

• struct drm_ras_node
• struct xe_drm_ras_counter
• struct xe_drm_ras
• enum hardware_error

Annotated Snippet

struct xe_drm_ras_counter {
	/** @name: error component name */
	const char *name;

	/** @counter: count of error */
	atomic_t counter;
};

/**
 * struct xe_drm_ras - XE DRM RAS structure
 *
 * This structure has details of error counters
 */
struct xe_drm_ras {
	/** @node: DRM RAS node */
	struct drm_ras_node *node;

	/** @info: info array for all types of errors */
	struct xe_drm_ras_counter *info[DRM_XE_RAS_ERR_SEV_MAX];
};

#endif

Annotation

• Immediate include surface: `linux/atomic.h`, `drm/xe_drm.h`.
• Detected declarations: `struct drm_ras_node`, `struct xe_drm_ras_counter`, `struct xe_drm_ras`, `enum hardware_error`.
• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.