amdgpu_amdkf...t_bo_to_gart(9)

📦 version 7.3.1, in nixpkgs unstable

💖 amdgpu_amdkf...t_bo_to_gart(9) 💖

okay so this is a page straight out of the Kernel API Manual (yes, the kernel has a manual, and yes it's iconic), and today's main character is amdgpu_amdkfd_map_gtt_bo_to_gart. buckle up bestie, it's short but it matters 🫶

✨ NAME ✨

amdgpu_amdkfd_map_gtt_bo_to_gart — literally maps a BO to GART and bumps the reference count. two jobs, one function, no cap 💅

🌸 SYNOPSIS 🌸

int amdgpu_amdkfd_map_gtt_bo_to_gart (struct amdgpu_bo *bo , struct
amdgpu_bo **bo_gart );

that's the whole signature, copy it exactly, don't get cute with it 🎀

🦋 ARGUMENTS 🦋

  • bo — the buffer object that's getting mapped. that's the one you're handing over 💖
  • bo_gart — the return bo reference. it comes back out through here, so heads up ✨

🔥 DESCRIPTION 🔥

so before this function returns, the bo reference count gets incremented. that's the little detail that'll bite you later if you forget it 👑

and here's the part where you listen: to release that reference and unpin/unmap the BO, you call amdgpu_amdkfd_free_kernel_mem. that's the cleanup, that's the vibes, that's the whole deal. don't just walk away from the reference you created, that's not main character energy, that's a leak 😭

💀 SEE ALSO 💀

the kernel file that lives at ./drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c — go read it, iykyk 📖

and the whole friend group, in this exact order:

real talk: the reference count increment is the whole trap here. increment it, then release it with amdgpu_amdkfd_free_kernel_mem, and unpin/unmap while you're at it. slay responsibly 🧚

and that's the page, bestie!! this lil gem lives in ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and it answers to the name amdgpu_amdkf...t_bo_to_gart(9) — yes the truncation is canon, we don't question it 💜 bye bye, go free your BOs 🌈⭐

📦 where this page comes from