drivers/gpu/drm/nouveau/nvkm/subdev/instmem/gh100.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/nouveau/nvkm/subdev/instmem/gh100.c

Extension

.c

Size

751 bytes

Lines

29

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

• priv.h
• nvhw/ref/gh100/pri_nv_xal_ep.h

Detected Declarations

• function Copyright
• function gh100_instmem_new

Annotated Snippet

#include "priv.h"

#include <nvhw/ref/gh100/pri_nv_xal_ep.h>

static void
gh100_instmem_set_bar0_window_addr(struct nvkm_device *device, u64 addr)
{
	nvkm_wr32(device, NV_XAL_EP_BAR0_WINDOW, addr >> NV_XAL_EP_BAR0_WINDOW_BASE_SHIFT);
}

static const struct nvkm_instmem_func
gh100_instmem = {
	.fini = nv50_instmem_fini,
	.memory_new = nv50_instobj_new,
	.memory_wrap = nv50_instobj_wrap,
	.set_bar0_window_addr = gh100_instmem_set_bar0_window_addr,
};

int
gh100_instmem_new(struct nvkm_device *device, enum nvkm_subdev_type type, int inst,
		  struct nvkm_instmem **pimem)
{
	return r535_instmem_new(&gh100_instmem, device, type, inst, pimem);
}

Annotation

• Immediate include surface: `priv.h`, `nvhw/ref/gh100/pri_nv_xal_ep.h`.
• Detected declarations: `function Copyright`, `function gh100_instmem_new`.
• 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.