i915_vma_resource_unhold(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ i915_vma_resource_unhold β€” the Kernel API Manual tea πŸ«–

okay bestie, so this one lives in the kernel API manual, and it's literally the "let go" half of a hold/unhold situationship πŸ’…


🌸 NAME 🌸

i915_vma_resource_unhold β€” unhold the signaling of the vma resource unbind fence. that's the whole gig, she's a one-job icon πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void i915_vma_resource_unhold (struct i915_vma_resource *vma_res , bool
       lockdep_cookie );

like, no return value, nothing to catch, she just does the thing and dips ✨


πŸ’– ARGUMENTS πŸ’–

  • vma_res β€” the vma resource. that's the vma resource, the main character of this function 🫢
  • lockdep_cookie β€” the lockdep cookie returned from i915_vma_resource_hold. yes bestie, you gotta bring back the cookie you got from the hold call, that's the whole deal πŸͺ β€” hand it over, no substitutions, no snacking on it.

🌈 DESCRIPTION 🌈

so here's the vibe: the function may leave a dma_fence critical section 😭 like, it might literally exit that critical section, so don't be out here assuming you're still cozy inside it after this call. that's the whole description and honestly it ate πŸ’…

ngl, "may leave a dma_fence critical section" is the kind of sentence you read twice β€” it's not a maybe-cute-maybe-not, it's a real caveat, so respect it πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

like, the whole friend group fr fr 🌸


<div align="center">βœ¨πŸ’œβœ¨</div>

and that's the page, bestie! courtesy of ./drivers/gpu/drm/i915, dropped October 2026, and stamped with i915_vma_resource_unhold(9) at the bottom like a little signature πŸŽ€ mwah πŸ’‹

πŸ“¦ where this page comes from