drivers/gpu/drm/xe/xe_mert.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_mert.c

Extension

.c

Size

3007 bytes

Lines

119

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

• regs/xe_irq_regs.h
• regs/xe_mert_regs.h
• xe_device.h
• xe_mert.h
• xe_mmio.h
• xe_sriov_printk.h
• xe_tile.h

Detected Declarations

• function Copyright
• function xe_mert_invalidate_lmtt
• function mert_handle_cat_error
• function xe_mert_irq_handler

Annotated Snippet

if (!(reg_val & MERT_TLB_INV_DESC_A_VALID)) {
			mert->tlb_inv_triggered = false;
			complete_all(&mert->tlb_inv_done);
		}
	}
	spin_unlock_irqrestore(&mert->lock, flags);
}

Annotation

• Immediate include surface: `regs/xe_irq_regs.h`, `regs/xe_mert_regs.h`, `xe_device.h`, `xe_mert.h`, `xe_mmio.h`, `xe_sriov_printk.h`, `xe_tile.h`.
• Detected declarations: `function Copyright`, `function xe_mert_invalidate_lmtt`, `function mert_handle_cat_error`, `function xe_mert_irq_handler`.
• 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.