i915_vma_resource_hold(9)

💅 i915_vma_resource_hold(9) — Kernel API Manual 🎀

okay so real talk, this is a page from the Kernel API Manual and it's about i915_vma_resource_hold, and honestly? she's short but she's important. let's get into it bestie ✨

---

🌸 NAME 🌸

i915_vma_resource_hold — hold the signaling of the vma resource unbind fence. that's it, that's the whole vibe. she holds the signal. no cap. 💅

---

✨ SYNOPSIS ✨

bool i915_vma_resource_hold (struct i915_vma_resource *vma_res , bool
*lockdep_cookie );

like, literally exactly that. don't @ me, that's the signature 🫶

---

🦋 ARGUMENTS 🦋

• vma_res — the vma resource itself. the main character of this whole situation 👑
• lockdep_cookie — a pointer to a bool that serves as a lockdep cooke, and bestie you do need to hand this same cookie over as an argument to the pairing i915_vma_resource_unhold. they're a matching set, don't separate them 😭 (and yes, the source really does spell it "cooke" — iconic, we love a typo that made it to production 🙈)

---

💖 DESCRIPTION 💖

so here's the tea: if this function returns true, it has entered a dma_fence signalling critical section — unless it was already in one, in which case, she was already there, she's not doing it twice 💀✨

---

🔥 RETURN 🔥

• true if holding was successful 🎉
• false if not 🙃

that's the whole vibe check, no in-between 🌈

---

🌟 SEE ALSO 🌟

• Kernel file ./drivers/gpu/drm/i915/i915_vma_resource.c
• Introduction(9)
• i915_vma_resource_alloc(9)
• i915_vma_resource_free(9)
• i915_vma_resource_unhold(9)
• i915_vma_resource_unbind(9)
• __i915_vma_resource_init(9)
• i915_vma_resource_bind_dep_sync(9)
• i915_vma_resource_bind_dep_sync_all(9)
• i915_vma_resource_bind_dep_await(9)

the whole friend group fr fr, go read them too 🫶💜

---

ngl this one's tiny but she's doing important fence work, treat her with respect ⭐

---

and that's a wrap bestie!! this page lives in ./drivers/gpu/drm/i915, dated October 2026, and it's literally called i915_vma_resource_hold(9) — slay, go hold some fences 💅🎀🦋