drivers/gpu/drm/i915/gem/selftests/mock_context.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/gem/selftests/mock_context.h

Extension

.h

Size

720 bytes

Lines

31

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct file
• struct drm_i915_private
• struct intel_engine_cs
• struct i915_address_space

Annotated Snippet

#ifndef __MOCK_CONTEXT_H
#define __MOCK_CONTEXT_H

struct file;
struct drm_i915_private;
struct intel_engine_cs;
struct i915_address_space;

void mock_init_contexts(struct drm_i915_private *i915);

struct i915_gem_context *
mock_context(struct drm_i915_private *i915,
	     const char *name);

void mock_context_close(struct i915_gem_context *ctx);

struct i915_gem_context *
live_context(struct drm_i915_private *i915, struct file *file);

struct i915_gem_context *kernel_context(struct drm_i915_private *i915,
					struct i915_address_space *vm);
void kernel_context_close(struct i915_gem_context *ctx);

#endif /* !__MOCK_CONTEXT_H */

Annotation

• Detected declarations: `struct file`, `struct drm_i915_private`, `struct intel_engine_cs`, `struct i915_address_space`.
• 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.