drivers/gpu/drm/i915/gt/intel_tlb.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/gt/intel_tlb.h

Extension

.h

Size

621 bytes

Lines

30

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/seqlock.h
• linux/types.h
• intel_gt_types.h

Detected Declarations

• function intel_gt_tlb_seqno
• function intel_gt_next_invalidate_tlb_full

Annotated Snippet

#ifndef INTEL_TLB_H
#define INTEL_TLB_H

#include <linux/seqlock.h>
#include <linux/types.h>

#include "intel_gt_types.h"

void intel_gt_invalidate_tlb_full(struct intel_gt *gt, u32 seqno);

void intel_gt_init_tlb(struct intel_gt *gt);
void intel_gt_fini_tlb(struct intel_gt *gt);

static inline u32 intel_gt_tlb_seqno(const struct intel_gt *gt)
{
	return raw_read_seqcount(&gt->tlb.seqno);
}

static inline u32 intel_gt_next_invalidate_tlb_full(const struct intel_gt *gt)
{
	return intel_gt_tlb_seqno(gt) | 1;
}

#endif /* INTEL_TLB_H */

Annotation

• Immediate include surface: `linux/seqlock.h`, `linux/types.h`, `intel_gt_types.h`.
• Detected declarations: `function intel_gt_tlb_seqno`, `function intel_gt_next_invalidate_tlb_full`.
• 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.