xe_hw_fence_init(9)

okay bestie, welcome to the Kernel API Manual page for xe_hw_fence_init — yes, that's a (9) page, we're in kernel-API girlie territory now 💅✨

🌸 NAME 🌸

xe_hw_fence_init — initialize an hw fence, periodt 🎀

✨ SYNOPSIS ✨

void xe_hw_fence_init (struct dma_fence *fence , struct xe_hw_fence_ctx *ctx , struct iosys_map seqno_map );

🦋 ARGUMENTS 🦋

• fence — pointer to the fence you're initializing, bestie. that's the main character right there 💖
• ctx — pointer to the struct xe_hw_fence_ctx fence context, aka the vibe context it lives in 🫶
• seqno_map — pointer to the map into where the seqno is blitted. yes, "blitted", that's the word, no cap ✨

🔥 DESCRIPTION 🔥

So basically: this initializes a pre-allocated hw fence. It's already been allocated — you're not making a new one here, you're just setting this one up, iykyk 👑

And after initialization? the fence is subject to normal dma-fence refcounting. literally normal refcounting, nothing cursed, nothing extra. slay 💅

ngl bestie, "pre-allocated" is doing a lot of work in that sentence — this function initializes it, it does not allocate it. keep that distinction close to your heart 🎀

🧚 SEE ALSO 🧚

• Kernel file ./drivers/gpu/drm/xe/xe_hw_fence.c
• xe_hw_fence_alloc(9)
• xe_hw_fence_free(9)

and that's the page, bestie 🫶 this cutie came from ./drivers/gpu/drm/xe, dated October 2026, and it's filed under xe_hw_fence_init(9) — iconic, no notes 💖✨🎀