xe_hw_engin...d_exec_queue(9)
π xe_hw_engine_group_add_exec_queue(9) π
okay so bestie, welcome to the Kernel API Manual β yes that's the manual name, we're in the big-kid kernel docs now π this little page is all about xe_hw_engine_group_add_exec_queue, which is exactly what it sounds like: you're shoving an exec queue into a hw engine group. iconic behaviour honestly.
β¨ NAME β¨
xe_hw_engine_group_add_exec_queue β add an exec queue to a hw engine group π«Ά
πΈ SYNOPSIS πΈ
int xe_hw_engine_group_add_exec_queue (struct xe_hw_engine_group *group
, struct xe_exec_queue *q );
like, that's the whole signature, no cap. it returns an int and takes two pointers. we love a clean two-arg function π
π¦ ARGUMENTS π¦
groupβ the hw engine group. this is the group you're adding to, your destination, your main character group πqβ the exec_queue. that's the queue being added, the lil newcomer joining the group π§
π RETURN π
0on success β slay, it worked β¨-EINTRif the lock could not be acquired β like the lock said "not right now bestie" π
π SEE ALSO π
the source file itself lives at:
Kernel file ./drivers/gpu/drm/xe/xe_hw_engine_group.c
and here's the whole lil friend group of related manpages, fr fr:
xe_hw_engine_setup_groups(9)xe_hw_engine_group_del_exec_queue(9)xe_hw_engine_group_resume_faulting_lr_jobs(9)xe_hw_engine_group_suspend_faulting_lr_jobs(9)xe_hw_engine_group_wait_for_dma_fence_jobs(9)xe_hw_engine_group_get_mode(9)xe_hw_engine_group_put(9)xe_hw_engine_group_find_exec_mode(9)
ngl, that's a whole squad of xe_hw_engine_group_* functions β read them together, iykyk π
and that's the page!! this one came out of the ./drivers/gpu/drm/xe tree, dated October 2026, and it insists on calling itself xe_hw_engin...d_exec_queue(9) (yes the abbreviation is cursed, we don't talk about it π). go forth and add those exec queues, 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