drm_gem_vram_vmap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_gem_vram_vmap(9) πŸ’–

okay bestie, welcome to your Kernel API Manual moment ✨ this is the page for drm_gem_vram_vmap, and it's giving β€œpin it, map it, don't leave it pinned forever” energy πŸ’… iykyk.


🌸 NAME 🌸

drm_gem_vram_vmap β€” Pins and maps a GEM VRAM object into kernel address space πŸ¦‹

✨ SYNOPSIS ✨

int drm_gem_vram_vmap (struct drm_gem_vram_object *gbo , struct
       iosys_map *map );

πŸŽ€ ARGUMENTS πŸŽ€

  • gbo β€” the GEM VRAM object to map, bestie πŸ’–
  • map β€” returns the kernel virtual address of the VRAM GEM object's backing store πŸ“

πŸ’« DESCRIPTION πŸ’«

so the vmap function pins a GEM VRAM object to its current location β€” either system memory or video memory β€” and maps its buffer into kernel address space ✨ that's the whole main character move.

⚠️ but listen: a pinned object cannot be relocated, so you should avoid pinning objects permanently. no cap, that's important πŸ’€

when you're done, call drm_gem_vram_vunmap with the returned address to unmap and unpin the GEM VRAM object 🫢

🌈 RETURN 🌈

0 on success, or a negative error code otherwise πŸ‘‘

πŸ¦‹ SEE ALSO πŸ¦‹


okay that's the whole vibe check πŸ’… β€” source/version lives at ./drivers/gpu/drm, dated October 2026. bye bestie 🫢✨

πŸ“¦ where this page comes from