STRUCT DRM_I915_GEM_TIMELINE_FENCE(9)

💅 struct drm_i915_gem_timeline_fence(9) 💅

okay so bestie, this is a page from the Kernel API Manual, and it's all about input or output timeline fence energy. Lowkey iconic, highkey specific. Let's go. 🦋

✨ NAME ✨

struct drm_i915_gem_timeline_fence — an input or output timeline fence. That's the name, that's the vibe, that's the whole point. 💖

🦋 SYNOPSIS 🦋

       struct drm_i915_gem_timeline_fence {
           __u32 handle;
           __u32 flags;
         #define I915_TIMELINE_FENCE_WAIT            (1 << 0);
         #define I915_TIMELINE_FENCE_SIGNAL          (1 << 1);
         #define __I915_TIMELINE_FENCE_UNKNOWN_FLAGS
       (-(I915_TIMELINE_FENCE_SIGNAL << 1));
           __u64 value;
        };

🫶 Members 🫶

• handle — the user's handle for a drm_syncobj to wait on or signal. It's your little ticket to either wait or signal, bestie. 🎟️
• flags — the supported flags are:
  • I915_TIMELINE_FENCE_WAIT — wait for the input fence before the operation. Yes, actually wait. ⏳
  • I915_TIMELINE_FENCE_SIGNAL — return the operation completion fence as output. Slay, output fence. 📤
• value — a point in the timeline. Value must be 0 for a binary drm_syncobj. A value of 0 for a timeline drm_syncobj is invalid, because it turns a drm_syncobj into a binary one. So like, don't do that. 🚫

🔥 Description 🔥

The operation will wait for the input fence to signal. Then the returned output fence will be signaled after the completion of the operation. That's the tea, and it's piping hot. 🍵

🌈 SEE ALSO 🌈

Kernel file: ./Documentation/gpu/rfc/i915_vm_bind.h

Also peep these, iykyk:

• I915_PARAM_VM_BIND_VERSION(9)
• I915_VM_CREATE_FLAGS_USE_VM_BIND(9)
• struct drm_i915_gem_vm_bind(9)
• struct drm_i915_gem_vm_unbind(9)
• struct drm_i915_gem_execbuffer3(9)
• struct drm_i915_gem_create_ext_vm_private(9)

mwah 💋 — this whole page is signed off from ./Documentation/gpu/rfc, dated October 2026. Go forth and timeline-fence responsibly, bestie. 🫶✨