amdgpu_vm_bo_del(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the amdgpu_vm_bo_del(9) page from the Kernel API Manual β€” yes, the manual name is folded right in here like a lil' name tag at the function meet-cute. 🫢 This one is short, sweet, and absolutely demands your object be reserved.

🌸 NAME 🌸

amdgpu_vm_bo_del β€” remove a bo from a specific vm. Literally it. πŸ’…

✨ SYNOPSIS ✨

void amdgpu_vm_bo_del (struct amdgpu_device *adev , struct amdgpu_bo_va
       *bo_va );

πŸŽ€ ARGUMENTS πŸŽ€

  • adev β€” amdgpu_device pointer. It's the device pointer, bestie. 🫢
  • bo_va β€” requested bo_va. The requested one, not a random one. πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

Remove bo_va->bo from the requested vm. That's the whole vibe: you point at the requested vm, and bo_va->bo gets removed from it. ✨

⚠️ Object have to be reserved! Like, this is not optional, bestie β€” the page is very clear about it. πŸ˜­πŸ’€

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c β€” main-character file behavior, honestly. And here are all the SEE ALSO besties, grouped for vibes but in the exact order the page lists them:


mwah πŸ’‹ β€” this lil' page came from <pink>./drivers/gpu/drm/amd/amdgpu</pink>, dated **October 2026**, and answers to **amdgpu_vm_bo_del(9)`**. That's the whole manual page, bestie β€” reserve that object and slay. πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from