xe_exec_queu...st_fence_put(9)
π xe_exec_queu...st_fence_put(9) π
okay so bestie, welcome to the Kernel API Manual page for xe_exec_queu...st_fence_put(9) β yes the title is literally truncated with an ellipsis, that's just how the kernel rolls, and we are not fixing it, we're respecting it π«Ά
β¨ NAME β¨
xe_exec_queue_tlb_inval_last_fence_put β no cap, this is the one that drops the ref to the last TLB invalidation fence π
It's giving "cleanup era" and honestly? Iconic. You're releasing a reference you were holding, and that is your whole job here π
π₯ SYNOPSIS π₯
void xe_exec_queue_tlb_inval_last_fence_put (struct xe_exec_queue *q ,
struct xe_vm *vm , unsigned int type );
Return type is void, so likeβ¦ don't expect a lil report card back. It just does the thing and leaves β¨
π¦ ARGUMENTS π¦
qβ The exec queue π§ this is your main character, the exec queue in question.vmβ The VM the engine does a bind for π that's the VM, doing a bind, for the engine. Slay.typeβ Either primary or media GT π so you gotta know which GT you're dealing with β primary or media, no in-between.
ngl, type being "either primary or media GT" is the vibes check you must pass before calling. Know your GT bestie π
π SEE ALSO π
the way this reference list just keeps going?? obsessed. Literally the whole exec queue friend group showed up π and also the file itself, obviously:
- Kernel file
./drivers/gpu/drm/xe/xe_exec_queue.cπΈ - Execution Queue(9)
- Multi Queue Group(9)
xe_exec_queue_get_lrc(9)xe_exec_queue_lrc(9)xe_exec_queue_create(9)xe_exec_queue_create_class(9)xe_exec_queue_create_bind(9)xe_exec_queue_destroy(9)xe_exec_queue_fini(9)xe_exec_queue_assign_name(9)xe_exec_queue_lookup(9)xe_exec_queue_device_get_max_priority(9)xe_exec_queue_set_property_ioctl(9)xe_exec_queue_create_ioctl(9)xe_exec_queue_get_property_ioctl(9)xe_exec_queue_is_lr(9)xe_exec_queue_is_idle(9)xe_exec_queue_update_run_ticks(9)xe_exec_queue_kill(9)xe_exec_queue_destroy_ioctl(9)xe_exec_queue_last_fence_put(9)xe_exec_queue_last_fence_put_unlocked(9)xe_exec_queue_last_fence_get(9)xe_exec_queue_last_fence_get_for_resume(9)xe_exec_queue_last_fence_set(9)xe_exec_queue_tlb_inval_last_fence_put_unlocked(9)xe_exec_queue_tlb_inval_last_fence_get(9)xe_exec_queue_tlb_inval_last_fence_set(9)xe_exec_queue_contexts_hwsp_rebase(9)
like bestieβ¦ the _put / _get / _set trio, the <italic>unlocked</italic> variants, the ioctls, the lrc crew β the whole family tree is right there. iykyk π
pro tip from one legend to another: if you clicked here looking for xe_exec_queue_tlb_inval_last_fence_put_unlocked(9), that is a different page. don't embarrass us π
and that's the whole page, periodt π β¨ go forth and drop that ref responsibly, bestie π«Ά
this lil number came to you from ./drivers/gpu/drm/xe β stamped October 2026, and yeah, the page is still called xe_exec_queu...st_fence_put(9) at the bottom too. consistency queen ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms