drivers/gpu/drm/nouveau/include/nvif/ifc00d.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/include/nvif/ifc00d.h

Extension

.h

Size

719 bytes

Lines

43

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

• if000c.h

Detected Declarations

• struct gp100_vmm_vn
• struct gp100_vmm_v0
• struct gp100_vmm_map_vn
• struct gp100_vmm_map_v0
• struct gp100_vmm_fault_replay_vn
• struct gp100_vmm_fault_cancel_v0

Annotated Snippet

struct gp100_vmm_vn {
	/* nvif_vmm_vX ... */
};

struct gp100_vmm_v0 {
	/* nvif_vmm_vX ... */
	__u8  version;
	__u8  fault_replay;
};

struct gp100_vmm_map_vn {
	/* nvif_vmm_map_vX ... */
};

struct gp100_vmm_map_v0 {
	/* nvif_vmm_map_vX ... */
	__u8  version;
	__u8  vol;
	__u8  ro;
	__u8  priv;
	__u8  kind;
};

#define GP100_VMM_VN_FAULT_REPLAY                         NVIF_VMM_V0_MTHD(0x00)
#define GP100_VMM_VN_FAULT_CANCEL                         NVIF_VMM_V0_MTHD(0x01)

struct gp100_vmm_fault_replay_vn {
};

struct gp100_vmm_fault_cancel_v0 {
	__u8  version;
	__u8  hub;
	__u8  gpc;
	__u8  client;
	__u8  pad04[4];
	__u64 inst;
};
#endif

Annotation

• Immediate include surface: `if000c.h`.
• Detected declarations: `struct gp100_vmm_vn`, `struct gp100_vmm_v0`, `struct gp100_vmm_map_vn`, `struct gp100_vmm_map_v0`, `struct gp100_vmm_fault_replay_vn`, `struct gp100_vmm_fault_cancel_v0`.
• 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.