amdgpu_bo_fence(9)

📦 version 7.3.1, in nixpkgs unstable

💅 amdgpu_bo_fence — like, the kernel API manual one, bestie

Okay so first things first: this page lives in the Kernel API Manual section 9, and the whole thing is called amdgpu_bo_fence. Yes, the title up top says it too. We're doing this together, you and me. 🫶

✨ NAME ✨

amdgpu_bo_fence — add fence to buffer object

Literally that's it. You're adding a fence. To a buffer object. Slay. 🎀

🌸 SYNOPSIS 🌸

void amdgpu_bo_fence (struct amdgpu_bo *bo , struct dma_fence *fence ,
       bool shared );

Three things go in, nothing comes out (it returns void, so don't be out here expecting a trophy). 🏆

💖 ARGUMENTS 💖

  • bo — the buffer object in question. Like, the subject of the whole operation. Main character energy fr fr. 👑
  • fence — the fence to add. This is the thing you're attaching. 🦋
  • shared — true if the fence should be added shared. That's the whole vibe check for this one. ✨

🔥 SEE ALSO 🔥

Okay bestie, buckle up, because this list is long and we are not skipping a single one of them — the manpage said so and I do not play about completeness. 💅

The kernel file in question, for the record:

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

And now the full squad, in order, no cap:

Every single one, accounted for. Obsessed with my own diligence honestly. 💀

Quick reminder that this whole page is the amdgpu_bo_fence(9) entry from the Kernel API Manual — so if you cite it, cite it right. 😌

And that's the tea! 🍓 Signing off from ./drivers/gpu/drm/amd/amdgpu — dated October 2026, and the manual name on the tin is amdgpu_bo_fence(9). Bye bestie, go add that fence! 🌈⭐💜

📦 where this page comes from