xe_exec_que...t_for_resume(9)
π xe_exec_que...t_for_resume(9) π
okay so bestie, welcome to the Kernel API Manual β¨ (yes the section header is literally truncated with ... in the middle, that's not me being lazy, that's just how the page rolls, ngl it's giving "not enough room in the terminal" energy π)
Today we're looking at xe_exec_queue_last_fence_get_for_resume β the snatch-the-fence-before-you-wake-the-engine-back-up function. Buckle in π¦
β¨ NAME β¨
xe_exec_queue_last_fence_get_for_resume β Get last fence π
Like. that's it. that's the whole name. she does what it says on the tin π
πΈ SYNOPSIS πΈ
struct dma_fence * xe_exec_queue_last_fence_get_for_resume (struct
xe_exec_queue *q , struct xe_vm *vm );
return type is struct dma_fence *, params are q and vm, that's the whole vibe fr fr π«Ά
π ARGUMENTS π
qβ The exec queue π like, the queue you're doing the thing withvmβ The VM the engine does a bind or exec for π
π§ DESCRIPTION π§
Get last fence, takes a ref. β¨
But β and this is the important part, the main-character caveat, no cap β it's only safe to be called in the context of resuming the hw engine group's long-running exec queue, when the group semaphore is held. π
bestie. bestie please read that again. only safe in that exact context. with the group semaphore held. don't just call it from anywhere like it's a free-for-all, that's not the vibe check we're passing here π
π₯ RETURN π₯
- last fence if not signaled π¦
- dma fence stub if signaled β
π SEE ALSO π
the whole friend group, the entire roster, iconic line-up honestly π:
- 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_set(9)xe_exec_queue_tlb_inval_last_fence_put(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)
okay and the vibe-signature π this whole page lives in ./drivers/gpu/drm/xe, dated October 2026, and the page itself answers to the name xe_exec_que...t_for_resume(9) π©· mwah, slay, go hold that semaphore bestie π
β¨π
π¦ 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