drm_gpuvm_exec_lock_array(9)

📦 version 7.3.1, in nixpkgs unstable

✨ drm_gpuvm_exec_lock_array(9) ✨

okay so bestie, welcome to the Kernel API Manual 💅 this one lives in the kernel chapter, and it's literally the "lock everything at once" girlie. let's get into it 🫶

🌸 NAME 🌸

drm_gpuvm_exec_lock_array — lock all dma-resv of all associated BOs 🔒

like, all of them. every single one. no cap.

🎀 SYNOPSIS 🎀

int drm_gpuvm_exec_lock_array (struct drm_gpuvm_exec *vm_exec ,
                               struct drm_gem_object **objs ,
                               unsigned int num_objs );

three args, one int back, that's the whole vibe ✨

🦋 ARGUMENTS 🦋

  • vm_exec — the drm_gpuvm_exec wrapper, aka the main character of this whole operation 👑
  • objs — additional drm_gem_objects to lock, like the plus-ones you're bringing to the lock party 🙈
  • num_objs — the number of additional drm_gem_objects to lock, i.e. how many plus-ones 💀

💜 DESCRIPTION 💜

so what does it actually do? it acquires all dma-resv locks of all drm_gem_objects that the given drm_gpuvm contains mappings of — plus the ones you handed it through objs. 🎯

it's giving "collect the whole squad and lock them all" energy, and honestly? iconic. the way that it doesn't miss a single one of the gpuvm's mapped objects, fr fr. 🔥

⭐ RETURN ⭐

  • 0 on success 🎉 (slay)
  • negative error code on failure 😭 (not slay, go check your error handling bestie)

🌈 SEE ALSO 🌈

okay this list is long — the kernel doc girlies really said "link everything" and honestly we respect it. all of these live in the kernel file ./drivers/gpu/drm/drm_gpuvm.c 📁

and that's the whole page, bestie 💖 before you go: this one's from ./drivers/gpu/drm, dated October 2026 — so like, mark your calendars 🗓️✨ mwah, go lock those resvs responsibly 🧚‍♀️💅

📦 where this page comes from