i915_gem_ob...moving_fence(9)
π i915_gem_object_wait_moving_fence(9)
Okay bestie, welcome to the Kernel API Manual β¨ β this one is all about i915_gem_object_wait_moving_fence, which honestly is the most "wait for the object's moving fence if any" function to ever wait for an object's moving fence if any. Lowkey iconic name. π
β¨ NAME β¨
i915_gem_object_wait_moving_fence β wait for the object's moving fence, if any π¦
(Yes, "if any." That's the whole vibe check. Not every object is out here having a moving fence, and that's fine.)
πΈ SYNOPSIS πΈ
int i915_gem_object_wait_moving_fence (struct drm_i915_gem_object *obj ,
bool intr );
That's the whole signature, no cap. She takes two things and returns an int. π
π ARGUMENTS π
objβ the object whose moving fence we're waiting for. Like, the actual main character of this operation. The object in question. The one with the fence. πintrβ whether to wait interruptible. That's it, that's the flag.trueif you want the wait to be interruptible, and you already know which one you're picking. π«Ά
π« DESCRIPTION π«
So here's the tea β: if the moving fence signaled without an error, it gets detached from the object and put. Like, removed and released. Clean break, no drama, we love to see it. β¨
That's genuinely the whole description, bestie β short and slay. Don't go looking for extra lore, there isn't any in the original. π
π₯ RETURN π₯
0β successful. Slay. π-ERESTARTSYSβ the wait was interrupted. π Somebody hit the interrupt, it wasn't me.- negative error code β the async operation represented by the moving fence failed. π That's the bad ending, fr fr.
π SEE ALSO π
Kernel file: ./drivers/gpu/drm/i915/gem/i915_gem_object.c
And the whole friend group, in order, no skips:
__i915_gem_object_fini(9)i915_gem_object_set_cache_coherency(9)i915_gem_object_set_pat_index(9)__i915_gem_object_pages_fini(9)i915_gem_object_read_from_page(9)i915_gem_object_evictable(9)i915_gem_object_migratable(9)i915_gem_object_has_struct_page(9)i915_gem_object_has_iomem(9)i915_gem_object_can_migrate(9)i915_gem_object_migrate(9)__i915_gem_object_migrate(9)i915_gem_object_placement_possible(9)i915_gem_object_needs_ccs_pages(9)i915_gem_object_get_moving_fence(9)
Like, go read i915_gem_object_get_moving_fence(9) next if you wanna know where the fence came from in the first place. iykyk. π§
Heads up bestie: this page lives under./drivers/gpu/drm/i915/gem, datedOctober 2026, and that's theKernel API Manualversion of the story. Go touch some pages. π
Okay bye, drink water, don't forget the intr argument, mwah ππ
π¦ 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