i915_gem_obj...moving_fence(9)

📦 version 7.3.1, in nixpkgs unstable

💅 i915_gem_obj...moving_fence(9)

okay bestie, welcome to the Kernel API Manual ✨ — this is the page for i915_gem_obj...moving_fence(9), and honestly? it's a short one, but it's lowkey important, so let's get into it 🫶

🌸 NAME 🌸

i915_gem_object_get_moving_fence — Get the object's moving fence if any 🎀

That's it. That's the whole name section. Slay.

✨ SYNOPSIS ✨

int i915_gem_object_get_moving_fence (struct drm_i915_gem_object *obj ,
struct dma_fence **fence );

literally verbatim, character for character, no cap 💅

🦋 ARGUMENTS 🦋

  • obj — The object whose moving fence to get. like, the object in question. the main character of this whole situation 👑
  • fence — The resulting fence — this is where the fence comes out 🎀

💖 DESCRIPTION 💖

so here's the vibe check 🔥 — a non-signaled moving fence means there's an async operation pending on the object. and that means you gotta wait on it before you go setting up any GPU- or CPU PTEs to the object's pages. no skipping ahead, bestie 😭 it's giving "please wait for your turn" energy.

iykyk — the fence isn't signaled yet, so the pages aren't ready. do not touch them until the wait is done. periodt 💀

🌈 RETURN 🌈

  • Negative error code — oops, something went wrong 🙈
  • 0 — for success ✨ we love to see it

⭐ SEE ALSO ⭐

like, the whole friend group fr fr 💜 go read them too, they're iconic.

🧚 that's the whole page, bestie. go forth and wait on your fences properly 💅

sign-off time 🎀 this lil gem lives in ./drivers/gpu/drm/i915/gem, and this edition is dated October 2026 — and yes, the page is literally titled i915_gem_obj...moving_fence(9) because truncation is giving minimal effort and honestly? iconic. 🦋✨

📦 where this page comes from