drivers/gpu/drm/i915/i915_gem_evict.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/i915_gem_evict.h

Extension

.h

Size

826 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

• linux/types.h

Detected Declarations

• struct drm_mm_node
• struct i915_address_space
• struct i915_gem_ww_ctx
• struct drm_i915_gem_object

Annotated Snippet

#ifndef __I915_GEM_EVICT_H__
#define __I915_GEM_EVICT_H__

#include <linux/types.h>

struct drm_mm_node;
struct i915_address_space;
struct i915_gem_ww_ctx;
struct drm_i915_gem_object;

int __must_check i915_gem_evict_something(struct i915_address_space *vm,
					  struct i915_gem_ww_ctx *ww,
					  u64 min_size, u64 alignment,
					  unsigned long color,
					  u64 start, u64 end,
					  unsigned flags);
int __must_check i915_gem_evict_for_node(struct i915_address_space *vm,
					 struct i915_gem_ww_ctx *ww,
					 struct drm_mm_node *node,
					 unsigned int flags);
int i915_gem_evict_vm(struct i915_address_space *vm,
		      struct i915_gem_ww_ctx *ww,
		      struct drm_i915_gem_object **busy_bo);

#endif /* __I915_GEM_EVICT_H__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct drm_mm_node`, `struct i915_address_space`, `struct i915_gem_ww_ctx`, `struct drm_i915_gem_object`.
• 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.