drm_gpuvm_prepare_range(9)

📦 version 7.3.1, in nixpkgs unstable

✨ drm_gpuvm_prepare_range(9) ✨

okay so this is a page from the Kernel API Manual, and bestie, it's about preparing all the BOs mapped inside a given range. it's giving "get your whole friend group ready before the group photo" energy ngl 💅

🌸 NAME 🌸

drm_gpuvm_prepare_range — prepare all BOs mapped within a given range

🎀 SYNOPSIS 🎀

int drm_gpuvm_prepare_range (struct drm_gpuvm *gpuvm , struct drm_exec
*exec , u64 addr , u64 range , unsigned int num_fences );

🦋 ARGUMENTS 🦋

  • gpuvm — the drm_gpuvm 💖 like, the actual GPU VM we're working with
  • exec — the drm_exec locking context ✨ your ticket to the lock party
  • addr — the start address within the VA space 📍
  • range — the range to iterate within the VA space 🧚
  • num_fences — the amount of dma_fences to reserve 🔥 no cap, this number matters

💜 DESCRIPTION 💜

So what it does: it calls drm_exec_prepare_obj for all drm_gem_objects mapped between addr and addr + range 💫 and if num_fences is zero, drm_exec_lock_obj is called instead. that's the whole vibe check — one little branch, two paths, both iconic 👑

⭐ RETURN ⭐

0 on success, negative error code on failure. periodt. 💅

fr fr, if you get a negative number back, something went sideways — that's your sign 🫶

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/drm_gpuvm.c — and honestly the whole extended fam:

like, that's a whole contact list, iykyk 🍓

and that's the page!! 🎀 source is ./drivers/gpu/drm, dated October 2026 — mwah, go read some more manpages bestie, ily 💖✨👑

📦 where this page comes from