drivers/gpu/drm/xe/xe_bb.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_bb.h

Extension

.h

Size

726 bytes

Lines

29

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

• xe_bb_types.h

Detected Declarations

• struct dma_fence
• struct xe_gt
• struct xe_exec_queue
• struct xe_sa_manager
• struct xe_sched_job

Annotated Snippet

#ifndef _XE_BB_H_
#define _XE_BB_H_

#include "xe_bb_types.h"

struct dma_fence;

struct xe_gt;
struct xe_exec_queue;
struct xe_sa_manager;
struct xe_sched_job;

struct xe_bb *xe_bb_new(struct xe_gt *gt, u32 dwords, bool usm);
struct xe_bb *xe_bb_alloc(struct xe_gt *gt);
int xe_bb_init(struct xe_bb *bb, struct xe_sa_manager *bb_pool, u32 dwords);
struct xe_sched_job *xe_bb_create_job(struct xe_exec_queue *q,
				      struct xe_bb *bb);
struct xe_sched_job *xe_bb_create_migration_job(struct xe_exec_queue *q,
						struct xe_bb *bb, u64 batch_ofs,
						u32 second_idx);
void xe_bb_free(struct xe_bb *bb, struct dma_fence *fence);

#endif

Annotation

• Immediate include surface: `xe_bb_types.h`.
• Detected declarations: `struct dma_fence`, `struct xe_gt`, `struct xe_exec_queue`, `struct xe_sa_manager`, `struct xe_sched_job`.
• 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.