xe_exec_que...put_unlocked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– xe_exec_queue_tlb_inval_last_fence_put_unlocked(9) πŸ’–

okay bestie, welcome to the Kernel API Manual corner of the group chat β€” yes, the (9) section, we're in kernel API territory now. this one is a whole mouthful of a function name but the vibe is very "destroy-time cleanup", so let's get into it 🫢✨


🌸 NAME 🌸

xe_exec_queue_tlb_inval_last_fence_put_unlocked β€” literally "Drop ref to last TLB invalidation fence unlocked". that's the whole name, no cap. it drops the reference to the last TLB invalidation fence, unlocked πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

the signature, bestie β€” copied exactly, character for character:

void xe_exec_queue_tlb_inval_last_fence_put_unlocked (struct
       xe_exec_queue *q , unsigned int type );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • q β€” The exec queue
  • type β€” Either primary or media GT

✨ DESCRIPTION ✨

okay so this function does the "drop ref to last TLB invalidation fence unlocked" thing from the name β€” and it returns void, so it's not handing you back a value or anything.

🚨 technical caveat time, bestie: Only safe to be called from xe_exec_queue_destroy.

like, that's the rule. it is only safe to be called from xe_exec_queue_destroy. do not just sprinkle this call around like glitter, okay? it's giving very specific destroy-time energy πŸ˜­πŸ’€


🌈 SEE ALSO 🌈

the whole squad is here, all the references, in order:


that's the whole page, bestie. source/version: ./drivers/gpu/drm/xe; date: October 2026. go be iconic with your exec queue cleanup πŸ’–βœ¨πŸ‘‘

πŸ“¦ where this page comes from