drivers/gpu/drm/i915/gvt/sched_policy.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/gvt/sched_policy.h

Extension

.h

Size

2248 bytes

Lines

66

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 intel_gvt
• struct intel_vgpu
• struct intel_gvt_sched_policy_ops

Annotated Snippet

struct intel_gvt_sched_policy_ops {
	int (*init)(struct intel_gvt *gvt);
	void (*clean)(struct intel_gvt *gvt);
	int (*init_vgpu)(struct intel_vgpu *vgpu);
	void (*clean_vgpu)(struct intel_vgpu *vgpu);
	void (*start_schedule)(struct intel_vgpu *vgpu);
	void (*stop_schedule)(struct intel_vgpu *vgpu);
};

void intel_gvt_schedule(struct intel_gvt *gvt);

int intel_gvt_init_sched_policy(struct intel_gvt *gvt);

void intel_gvt_clean_sched_policy(struct intel_gvt *gvt);

int intel_vgpu_init_sched_policy(struct intel_vgpu *vgpu);

void intel_vgpu_clean_sched_policy(struct intel_vgpu *vgpu);

void intel_vgpu_start_schedule(struct intel_vgpu *vgpu);

void intel_vgpu_stop_schedule(struct intel_vgpu *vgpu);

void intel_gvt_kick_schedule(struct intel_gvt *gvt);

#endif

Annotation

• Detected declarations: `struct intel_gvt`, `struct intel_vgpu`, `struct intel_gvt_sched_policy_ops`.
• 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.