i915_vma_pin_fence(9)
π 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:
i915_vma_size(9)i915_vma_offset(9)i915_vma_pin_iomap(9)i915_vma_unpin_iomap(9)i915_vma_unpin_fence(9)for_each_ggtt_vma(9)i915_vma_get_current_resource(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms