STRUCT XE_HW_FENCE(9)

💅 struct xe_hw_fence(9) 💅

ok so bestie, welcome to the manual page for struct xe_hw_fence — aka the hardware fence — straight out of the Linux Kernel API Manual, no cap. this is a kernel API page, so grab a lil snack and let's get into it 🍓

---

✨ SYNOPSIS ✨

like, here's the whole entire struct, character for character, because you KNOW we don't mess with the code:

struct xe_hw_fence {
    struct dma_fence dma;
    struct xe_device *xe;
    char name[MAX_FENCE_NAME_LEN];
    struct iosys_map seqno_map;
    struct list_head irq_link;
 };

that's the whole vibe. five members. iconic. 🎀

---

🌸 MEMBERS 🌸

• dma — the base dma fence for a hardware fence context. it's giving "foundation of the whole operation" energy, honestly.
• xe — the Xe device, and it's here for the hw fence driver name. yeah. that's its whole job. 💜
• name — the name of the hardware fence context. so it can introduce itself at parties, lowkey.
• seqno_map — an I/O map for seqno. mapping queen 👑
• irq_link — the link in struct xe_hw_fence_irq.pending. it's literally in the pending list, and that's the whole story bestie.

---

🦋 DESCRIPTION 🦋

ok so here's the actual tea 🫖 — this struct is used to indicate that a xe_sched_job is complete, and it does that via a seqno written to memory. that's it, that's the function. signals on error or seqno past. periodt. ✨

ngl this part is short but it's important — signals on error or seqno past means the fence wakes up in either of those cases, and that's as much as the page tells us so we're not gonna invent anything else 🙈

---

🧚 SEE ALSO 🧚

• the kernel file ./drivers/gpu/drm/xe/xe_hw_fence_types.h
• struct xe_hw_fence_irq(9)
• struct xe_hw_fence_ctx(9)

go read those next bestie, the lore is deep 🌈

---

and that's a wrap!! this lil gem comes from ./drivers/gpu/drm/xe, dated October 2026, and it lives in the Kernel API Manual as struct xe_hw_fence(9). mwah 💋 slay, go write some fences 🎀💖