drivers/gpu/drm/xe/xe_mert.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_mert.h

Extension

.h

Size

856 bytes

Lines

36

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

Detected Declarations

• struct xe_device
• struct xe_mert
• function xe_mert_irq_handler

Annotated Snippet

struct xe_mert {
	/** @lock: protects the TLB invalidation status */
	spinlock_t lock;
	/** @tlb_inv_triggered: indicates if TLB invalidation was triggered */
	bool tlb_inv_triggered;
	/** @tlb_inv_done: completion of TLB invalidation */
	struct completion tlb_inv_done;
};

#ifdef CONFIG_PCI_IOV
void xe_mert_init_early(struct xe_device *xe);
int xe_mert_invalidate_lmtt(struct xe_device *xe);
void xe_mert_irq_handler(struct xe_device *xe, u32 master_ctl);
#else
static inline void xe_mert_irq_handler(struct xe_device *xe, u32 master_ctl) { }
#endif

#endif

Annotation

• Immediate include surface: `linux/completion.h`, `linux/spinlock.h`, `linux/types.h`.
• Detected declarations: `struct xe_device`, `struct xe_mert`, `function xe_mert_irq_handler`.
• 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.