xe_sync_in_fence_get(9)

💖 xe_sync_in_fence_get(9) 💖

okay bestie, welcome to the kernel API manual for xe_sync_in_fence_get — the xe_sync_in_fence_get page, live from the Kernel API Manual, and yes we are absolutely getting into it 🎀

---

✨ NAME ✨

xe_sync_in_fence_get — get a fence from syncs, exec queue, and VM 🦋

✨ SYNOPSIS ✨

struct dma_fence * xe_sync_in_fence_get (struct xe_sync_entry *sync ,
int num_sync , struct xe_exec_queue *q , struct xe_vm *vm );

✨ ARGUMENTS ✨

• sync — the input syncs, aka the whole vibe you're handing in 💅
• num_sync — how many syncs there are, bestie. count them. 🔢
• q — the exec queue 👑
• vm — the VM 🌸

✨ DESCRIPTION ✨

okay so the whole point: this gets a fence from the syncs, the exec queue, and the VM. that's literally the job.

if the syncs contain in-fences, it creates and returns a composite fence made of all the in-fences plus the last fence. iconic behavior, no cap 🫶

if there are no in-fences, it just returns the last fence on the input exec queue. simple. clean. slay.

⚠️ heads up bestie: the caller must drop the reference to the returned fence. not optional, not vibes-based, actually do it 😭

✨ RETURN ✨

• a fence on success 💖
• ERR_PTR(-ENOMEM) on failure 💀

✨ SEE ALSO ✨

check the kernel file ./drivers/gpu/drm/xe/xe_sync.c for xe_sync_entry_wait(9), xe_sync_needs_wait(9), __xe_sync_ufence_get(9), xe_sync_ufence_get(9), xe_sync_ufence_put(9), xe_sync_ufence_get_status(9) 🌈

---

and that's the page, bestie! this one's from ./drivers/gpu/drm/xe, dated October 2026 — go forth and get those fences, you've got main character energy ⭐💜