i915_vma_pin_fence(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… i915_vma_pin_fence β€” a Kernel API Manual moment

okay so bestie, welcome to the i915_vma_pin_fence(9) page πŸ’– this is from the Kernel API Manual and it's lowkey iconic, so let's get into it ✨


🌸 NAME 🌸

i915_vma_pin_fence β€” pin fencing state πŸŽ€


✨ SYNOPSIS ✨

int i915_vma_pin_fence (struct i915_vma *vma );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • vma β€” the vma you're pinning fencing for, like that's her job now πŸ’…

πŸ’œ DESCRIPTION πŸ’œ

So what this does is it pins the fencing state β€” and yes that means whether it's tiled or untiled, both count 🫢 β€” to make sure the vma (and its object, can't forget the object, they're a package deal fr fr) is ready to be used as a scanout target. main character energy only 🌟

⚠️ but listen, the fencing status must be synchronized first by calling i915_vma_get_fence β€” don't skip this step bestie, it's giving prerequisites 😭

And then the resulting fence pin reference must be released again with i915_vma_unpin_fence. like, you can't just leave it pinned, that's not the vibe πŸ™ˆ


πŸ‘‘ RETURN πŸ‘‘

True if the vma has a fence, false otherwise. simple as that, no cap πŸ’€


🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/i915/i915_vma.h plus the whole friend group:


and that's the page!! πŸ“ this cutie lives over in ./drivers/gpu/drm/i915, dated October 2026, brought to you by the Kernel API Manual itself 🧚 mwah, go read your fences properly, ily πŸ’œ

πŸ“¦ where this page comes from