drivers/gpu/drm/xe/xe_ttm_stolen_mgr.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_ttm_stolen_mgr.h

Extension

.h

Size

859 bytes

Lines

34

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 ttm_resource
• struct xe_bo
• struct xe_device
• struct xe_ttm_stolen_mgr

Annotated Snippet

struct xe_ttm_stolen_mgr {
	/** @io_base: PCI base offset for CPU I/O access */
	resource_size_t io_base;
	/** @stolen_base: GPU base offset */
	resource_size_t stolen_base;
	/** @mapping: I/O memory mapping for CPU access */
	void __iomem *mapping;
};

int xe_ttm_stolen_mgr_init(struct xe_device *xe);
int xe_ttm_stolen_io_mem_reserve(struct xe_device *xe, struct ttm_resource *mem);
bool xe_ttm_stolen_cpu_access_needs_ggtt(struct xe_device *xe);
u64 xe_ttm_stolen_io_offset(struct xe_bo *bo, u32 offset);
u64 xe_ttm_stolen_gpu_offset(struct xe_device *xe);

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct ttm_resource`, `struct xe_bo`, `struct xe_device`, `struct xe_ttm_stolen_mgr`.
• 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.