amdgpu_vm_bo_unmap(9)

📦 version 7.3.1, in nixpkgs unstable

💅 amdgpu_vm_bo_unmap(9) — the Kernel API Manual, bestie edition 🎀

okay so welcome to the glow-up of amdgpu_vm_bo_unmap(9), straight out of the Kernel API Manual. this is the little function that un-maps a buffer object from a VM. it's giving "breakup but make it tidy" energy, and honestly? iconic. let's get into it ✨

🌸 NAME 🌸

amdgpu_vm_bo_unmap — remove bo mapping from vm. that's the whole vibe, no cap. 🦋

✨ SYNOPSIS ✨

int amdgpu_vm_bo_unmap (struct amdgpu_device *adev , struct amdgpu_bo_va
*bo_va , uint64_t saddr );

so you call it with three things and it hands you back an int. simple, clean, hydrated. 💧

🫶 ARGUMENTS 🫶

  • adev — the amdgpu_device pointer, aka your whole GPU situation. main character energy, fr. 👑
  • bo_va — the bo_va you're pulling the address out of. this is the one getting un-mapped. 💔
  • saddr — where the BO is mapped. like, the address. the spot. that one. 📍

🔥 DESCRIPTION 🔥

so basically this removes a mapping of the BO at the specified address from the VM. that's it, that's the function. literally its whole job and it does it slayfully 💅

⚠️ okay but here's the part you CANNOT skip, bestie: the object has to be reserved and unreserved outside! this function does not do that for you. not its lane, not its problem. so lock it up yourself before, and unlock it after. do not make me come over there 😭

⭐ RETURN ⭐

  • 0 for success 🎉 (we love a zero)
  • error for failure 💀 (we do not love this, but it happens)

🎀 SEE ALSO 🎀

the friend group. the whole group chat. every single one of them, fr fr:

and that's the whole page, bestie 🫶 this came to you from ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and it's amdgpu_vm_bo_unmap(9) — the one and only. go forth, reserve and unreserve that object properly, and remember: un-map responsibly 💜🌸✨

📦 where this page comes from