xe_exec_que...put_unlocked(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_exec_queue_last_fence_put_unlocked — Kernel API Manual 💅

okay so bestie, welcome to the glow-up era of xe_exec_queue_last_fence_put_unlocked(9). this is a Kernel API Manual page and it's serving very specific energy — it's the "unlocked" sibling, and it has ✨opinions✨ about where you're allowed to call it from. let's get into it 🎀

✨ NAME ✨

xe_exec_queue_last_fence_put_unlocked — drop ref to last fence, unlocked. that's it, that's the whole vibe. lowkey minimalist queen 💅

🌸 SYNOPSIS 🌸

void xe_exec_queue_last_fence_put_unlocked (struct xe_exec_queue *q );

literally one function, one argument, void return. no drama. she ate and left no crumbs 🫶

🦋 ARGUMENTS 🦋

  • q — the exec queue 💖. yes that's the entire description. iconic brevity, no notes.

🔥 DESCRIPTION 🔥

so here's the tea, and it is important tea: this function is only safe to be called from xe_exec_queue_destroy. no cap, fr fr. 🚨

that's not a suggestion, that's not a "probably fine", that's the actual rule. if you call it from anywhere else you are on your own, bestie, and I cannot help you 😭. think of it as a members-only party and the only guest list is xe_exec_queue_destroy. the way that this function trusts you to use it correctly is honestly main character energy but also terrifying 💀

⭐ SEE ALSO ⭐

the friend group is huge, okay, she knows everybody 🐝:

like I said. huge friend group. 30 whole entries. she's popular 💜

quick reminder bestie: unlocked means unlocked, and "only safe from xe_exec_queue_destroy" means only safe from xe_exec_queue_destroy. don't be the person who finds out the hard way 🙈

✨ and that's the page! ✨ this little love letter lives in ./drivers/gpu/drm/xe, dated October 2026, in the Kernel API Manual — mwah, catch you in the next manpage, bestie, ily 🎀💖🌸

📦 where this page comes from