amdgpu_amdkfd_gpuvm_pin_bo(9)

💖 amdgpu_amdkfd_gpuvm_pin_bo(9) 💖

okay so bestie, welcome to the Kernel API Manual entry for amdgpu_amdkfd_gpuvm_pin_bo — yes that's a mouthful, no I will not be shortening it, it's iconic as-is 💅

---

✨ NAME ✨

amdgpu_amdkfd_gpuvm_pin_bo — pins a BO using the following criteria 🎀

---

🦋 SYNOPSIS 🦋

int amdgpu_amdkfd_gpuvm_pin_bo (struct amdgpu_bo *bo , u32 domain );

like, that's the whole signature, look at her go 😭

---

🌸 ARGUMENTS 🌸

• bo — the handle of the buffer object that's getting pinned. that's your main character right there 👑
• domain — the domain the BO should be pinned into. yes, you gotta tell it where to live 🏠

---

💜 DESCRIPTION 💜

so here's the vibe check on what actually happens:

• USERPTR BOs are UNPINNABLE and will return error. fr fr, do not try it, it's giving "no ❌"
• every other BO type (GTT, VRAM, MMIO and DOORBELL) gets its PIN count incremented. and ngl, it's totally valid to PIN a BO multiple times — stack those pins, slay 🔥

---

⭐ RETURN ⭐

ZERO if it pinned successfully 🫶 — Non-Zero if there was an error 💀

---

🌈 SEE ALSO 🌈

the kernel file, bestie, in all her glory:

./drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c

and the whole friend group of related pages (iykyk):

• reuse_dmamap(9)
• amdgpu_amdkfd_reserve_mem_limit(9)
• create_dmamap_sg_bo(9)
• amdgpu_amdkfd_remove_all_eviction_fences(9)
• create_sg_table(9)
• kfd_mem_dmamap_sg_bo(9)
• kfd_mem_dmaunmap_sg_bo(9)
• reserve_bo_and_vm(9)
• reserve_bo_and_cond_vms(9)
• unreserve_bo_and_vms(9)
• amdgpu_amdkfd_gpuvm_unpin_bo(9)
• amdgpu_amdkfd_map_gtt_bo_to_gart(9)

---

🧚 quick reminder: this page comes from ./drivers/gpu/drm/amd/amdgpu, dated October 2026, in the Kernel API Manual. that's the whole sign-off bestie — go pin some BOs responsibly 💖✨🎀