drm_gem_dmabuf_vmap(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_gem_dmabuf_vmap(9) — like, the Kernel API Manual page for it, bestie 🎀

okay so this is drm_gem_dmabuf_vmap from the Kernel API Manual, and it's literally the whole "dma_buf vmap implementation for GEM" situation. yes that's the NAME section, don't @ me ✨

🌸 SYNOPSIS 🌸

int drm_gem_dmabuf_vmap (struct dma_buf *dma_buf , struct iosys_map *map );

like, it takes two things and returns an int. that's it. that's the whole vibe 🫶

🦋 ARGUMENTS 🦋

  • dma_buf — the buffer that's getting mapped, bestie. the actual thing. 💖
  • map — the virtual address of the buffer. where it goes. 👑

💜 DESCRIPTION 💜

So what it does — it sets up a kernel virtual mapping. no cap, that's the job. 🧚

You can use this as the dma_buf_ops.vmap callback — like, that's genuinely what it's for, iykyk. It then calls into drm_gem_object_funcs.vmap for the device specific handling, because the driver gets to have its main character moment too. 💅

The kernel virtual address is returned in map. so that's where you look for it, okay? don't go hunting elsewhere. 🌈

It returns 0 on success, or a negative errno code otherwise. periodt. 💀

⭐ SEE ALSO ⭐

okay this list is long bestie, but here's the whole thing, no skipping, we eat the whole plate 🍓:

ngl the whole PRIME friend group is here. read the ./drivers/gpu/drm/drm_prime.c overview first if you want the lore, and definitely check the lifetime rules because lifetime stuff is where things get spicy 😭

👑 sign-off 👑

this lil page lives in ./drivers/gpu/drm (yes, the source folder, that tracks), dated October 2026. that's the version and the date, mentioned cutely, as one does. bye bestie, go map something 💖✨🎀

📦 where this page comes from