i915_active_fence_get(9)

💅 i915_active_fence_get(9) — like, the Kernel API Manual, bestie

okay so picture this: you're deep in the Kernel API Manual and you need a reference to the active fence. this is THE page for that. no cap. 🦋

---

✨ NAME ✨

i915_active_fence_get — returns a reference to the active fence. that's the whole vibe. 🎀

✨ SYNOPSIS ✨

struct dma_fence * i915_active_fence_get (struct i915_active_fence
*active );

literally just hand it the tracker and it hands you back a fence. iconic behavior. 💅

✨ ARGUMENTS ✨

• active — the active tracker. that's it, that's the one. give it the active tracker and it'll do its thing. 🫶

✨ DESCRIPTION ✨

so what does i915_active_fence_get actually do? it returns a reference to the active fence, or NULL if the active tracker is idle. like, if nothing's going on, you get NULL. that's your signal. no fence, no drama. 😭

the reference is obtained under RCU — meaning the caller doesn't have to do any locking. none. zero. not a single lock. the RCU is handling it, you're just living your life. ✨

🚨 okay this part MATTERS bestie: the reference should be freed with dma_fence_put. do not forget. do not ghost it. free the reference. periodt. 💀

✨ SEE ALSO ✨

• Kernel file ./drivers/gpu/drm/i915/i915_active.h 👑
• __i915_active_fence_init(9)
• i915_active_fence_set(9)
• i915_active_fence_isset(9)

go read those too, they're all in the same friend group fr fr. 🌸

---

🦋 and that's the page! brought to you by the fine folks over at ./drivers/gpu/drm/i915, dated October 2026, living under the i915_active_fence_get(9) banner in the Kernel API Manual. slay, stay locked, and put that fence when you're done. mwah 💖✨