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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

2188 bytes

Lines

60

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 intel_vgpu
• struct intel_vgpu_page_track
• struct intel_vgpu_page_track

Annotated Snippet

struct intel_vgpu_page_track {
	gvt_page_track_handler_t handler;
	bool tracked;
	void *priv_data;
};

struct intel_vgpu_page_track *intel_vgpu_find_page_track(
		struct intel_vgpu *vgpu, unsigned long gfn);

int intel_vgpu_register_page_track(struct intel_vgpu *vgpu,
		unsigned long gfn, gvt_page_track_handler_t handler,
		void *priv);
void intel_vgpu_unregister_page_track(struct intel_vgpu *vgpu,
		unsigned long gfn);

int intel_vgpu_enable_page_track(struct intel_vgpu *vgpu, unsigned long gfn);
int intel_vgpu_disable_page_track(struct intel_vgpu *vgpu, unsigned long gfn);

int intel_vgpu_page_track_handler(struct intel_vgpu *vgpu, u64 gpa,
		void *data, unsigned int bytes);

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct intel_vgpu`, `struct intel_vgpu_page_track`, `struct intel_vgpu_page_track`.
• 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.