drm_gpuvm_sm...ap_exec_lock(9)

💅 drm_gpuvm_sm_unmap_exec_lock(9) — a Kernel API Manual moment

okay bestie, sit down, because this is a kernel API manual page and the name up top is drm_gpuvm_sm_unmap_exec_lock(9) — yes, the manpage header is out here getting cropped like drm_gpuvm_sm...ap_exec_lock(9), we don't know her full government name in the title bar but we do know it, and it's giving "locking, but make it unmap."

---

✨ NAME ✨

drm_gpuvm_sm_unmap_exec_lock — locks the objects touched by drm_gpuvm_sm_unmap()

like literally that's the whole job. she locks. that's it. that's the girl. 🔒

---

🦋 SYNOPSIS 🦋

int drm_gpuvm_sm_unmap_exec_lock (struct drm_gpuvm *gpuvm , struct
drm_exec *exec , u64 req_addr , u64 req_range );

she returns an int, she takes four args, no cap. 🫶

---

🎀 ARGUMENTS 🎀

• gpuvm — the struct drm_gpuvm that's out here representing the GPU VA space. main character energy, honestly.
• exec — the struct drm_exec locking context. this is the vibe check container, basically.
• req_addr — the start address of the range you're about to unmap. u64, because addresses are long and so is this week.
• req_range — the range of the mappings to unmap. also u64. also slay.

---

🌸 DESCRIPTION 🌸

so what does she do. this function locks — specifically via drm_exec_lock_obj — the objects that will be unmapped/remapped by drm_gpuvm_sm_unmap. that's it, that's the tea 💅

and if you're sitting there like "okay but how am i supposed to use this," the page is literally pointing you at your other bestie: see drm_gpuvm_sm_map_exec_lock for expected usage. iykyk 🧚

---

⭐ RETURN ⭐

0 on success ✨ — or a negative error code 😭

that's the whole return value situation. no notes.

---

🔥 SEE ALSO 🔥

the kernel file lives at ./drivers/gpu/drm/drm_gpuvm.c, and she brought her entire friend group. every single one, no gatekeeping:

• Overview(9)
• Split and Merge(9)
• Madvise Logic - Splitting and Traversal(9)
• Locking(9)
• Examples(9)
• get_next_vm_bo_from_list(9)
• for_each_vm_bo_in_list(9)
• restore_vm_bo_list(9)
• drm_gpuvm_bo_is_zombie(9)
• drm_gpuvm_bo_list_add(9)
• drm_gpuvm_bo_list_del_init(9)
• drm_gpuvm_bo_list_del(9)
• drm_gpuvm_range_valid(9)
• drm_gpuvm_resv_object_alloc(9)
• drm_gpuvm_init(9)
• drm_gpuvm_put(9)
• drm_gpuvm_prepare_vm(9)
• drm_gpuvm_prepare_objects(9)
• drm_gpuvm_prepare_range(9)
• drm_gpuvm_exec_lock(9)
• drm_gpuvm_exec_lock_array(9)
• drm_gpuvm_exec_lock_range(9)
• drm_gpuvm_validate(9)
• drm_gpuvm_resv_add_fence(9)
• drm_gpuvm_bo_create(9)
• drm_gpuvm_bo_put(9)
• drm_gpuvm_bo_put_deferred(9)
• drm_gpuvm_bo_deferred_cleanup(9)
• drm_gpuvm_bo_find(9)
• drm_gpuvm_bo_obtain_locked(9)
• drm_gpuvm_bo_obtain_prealloc(9)
• drm_gpuvm_bo_extobj_add(9)
• drm_gpuvm_bo_evict(9)
• drm_gpuva_insert(9)
• drm_gpuva_remove(9)
• drm_gpuva_link(9)
• drm_gpuva_unlink(9)
• drm_gpuva_unlink_defer(9)
• drm_gpuva_find_first(9)
• drm_gpuva_find(9)
• drm_gpuvm_interval_empty(9)
• drm_gpuva_map(9)
• drm_gpuva_remap(9)
• drm_gpuva_unmap(9)
• drm_gpuvm_sm_map(9)
• drm_gpuvm_sm_unmap(9)
• drm_gpuvm_sm_map_exec_lock(9)
• drm_gpuvm_sm_map_ops_create(9)
• drm_gpuvm_madvise_ops_create(9)
• drm_gpuvm_sm_unmap_ops_create(9)
• drm_gpuvm_prefetch_ops_create(9)
• drm_gpuvm_bo_unmap_ops_create(9)
• drm_gpuva_ops_free(9)

like... the whole roster. 💀 she said "you WILL know my friends."

---

lowkey reminder bestie: this is the locking half, not the map/unmap itself. drm_gpuvm_sm_unmap() is the one doing the unmapping — this one is backstage holding the objects down. 🫶

---

and that's the page!! 🎀 sourced from ./drivers/gpu/drm, dated October 2026, part of the Kernel API Manual — mwah, go lock some objects responsibly, ily, bye 👑✨