xe_gt_sriov_...antum_locked(9)
π xe_gt_sriov_...antum_locked(9)
okay bestie so this is from the Kernel API Manual (yes, the whole manual, we're fancy now) and the page header is literally xe_gt_sriov_...antum_locked(9) β yes it's abbreviated, yes it's giving "we ran out of column inches," no we don't talk about it π
β¨ NAME β¨
xe_gt_sriov_pf_config_bulk_set_exec_quantum_locked β configures the EQ for the PF and all the VFs. bulk energy, group-chat energy, one call and everybody gets the memo π«Ά
π SYNOPSIS π
int xe_gt_sriov_pf_config_bulk_set_exec_quantum_locked (struct xe_gt *gt
, u32 exec_quantum );
πΈ ARGUMENTS πΈ
gtβ thexe_gtyou're configuring. that's the one, that's the target π―exec_quantumβ the execution quantum you're requesting, in milliseconds. and listen:0is infinity β no cap, zero means forever, that's just how it is.
π¦ DESCRIPTION π¦
This function can only be called on the PF with the master mutex held. like, held-held. if you don't have the master mutex, this is not your moment, bestie π not a vibe, not a slay, just don't.
fr fr β PF only, master mutex held. that's the whole vibe check for this one.
π RETURN π
0on success π slay- a negative error code on failure π it's giving "not today"
π SEE ALSO π
the kernel file you want is right here, go read it: ./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
and here's the entire friend group, everyone's invited to the function party π:
xe_gt_sriov_pf_config_get_ggtt(9)xe_gt_sriov_pf_config_set_ggtt(9)xe_gt_sriov_pf_config_bulk_set_ggtt(9)xe_gt_sriov_pf_config_set_fair_ggtt(9)xe_gt_sriov_pf_config_ggtt_save(9)xe_gt_sriov_pf_config_ggtt_restore(9)xe_gt_sriov_pf_config_get_ctxs(9)xe_gt_sriov_pf_config_set_ctxs(9)xe_gt_sriov_pf_config_bulk_set_ctxs(9)xe_gt_sriov_pf_config_set_fair_ctxs(9)xe_gt_sriov_pf_config_get_dbs(9)xe_gt_sriov_pf_config_set_dbs(9)xe_gt_sriov_pf_config_bulk_set_dbs(9)xe_gt_sriov_pf_config_set_fair_dbs(9)xe_gt_sriov_pf_config_get_lmem(9)xe_gt_sriov_pf_config_set_lmem(9)xe_gt_sriov_pf_config_bulk_set_lmem_locked(9)xe_gt_sriov_pf_config_bulk_set_lmem(9)xe_gt_sriov_pf_config_get_lmem_locked(9)xe_gt_sriov_pf_config_set_lmem_locked(9)xe_gt_sriov_pf_config_get_lmem_obj(9)xe_gt_sriov_pf_config_set_fair_lmem(9)xe_gt_sriov_pf_config_set_fair(9)xe_gt_sriov_pf_config_set_exec_quantum_locked(9)xe_gt_sriov_pf_config_set_exec_quantum(9)xe_gt_sriov_pf_config_get_exec_quantum_locked(9)xe_gt_sriov_pf_config_get_exec_quantum(9)xe_gt_sriov_pf_config_set_groups_exec_quantums(9)xe_gt_sriov_pf_config_get_groups_exec_quantums(9)xe_gt_sriov_pf_config_set_preempt_timeout_locked(9)xe_gt_sriov_pf_config_set_preempt_timeout(9)xe_gt_sriov_pf_config_get_preempt_timeout_locked(9)xe_gt_sriov_pf_config_get_preempt_timeout(9)xe_gt_sriov_pf_config_bulk_set_preempt_timeout_locked(9)xe_gt_sriov_pf_config_set_groups_preempt_timeouts(9)xe_gt_sriov_pf_config_get_groups_preempt_timeouts(9)xe_gt_sriov_pf_config_set_sched_priority(9)xe_gt_sriov_pf_config_get_sched_priority(9)xe_gt_sriov_pf_config_force_sched_priority_locked(9)xe_gt_sriov_pf_config_set_fair_sched(9)xe_gt_sriov_pf_config_set_threshold(9)xe_gt_sriov_pf_config_get_threshold(9)xe_gt_sriov_pf_config_release(9)xe_gt_sriov_pf_config_sanitize(9)xe_gt_sriov_pf_config_push(9)xe_gt_sriov_pf_config_is_empty(9)xe_gt_sriov_pf_config_save(9)xe_gt_sriov_pf_config_restore(9)xe_gt_sriov_pf_config_init(9)xe_gt_sriov_pf_config_restart(9)xe_gt_sriov_pf_config_print_ggtt(9)xe_gt_sriov_pf_config_print_ctxs(9)xe_gt_sriov_pf_config_print_dbs(9)xe_gt_sriov_pf_config_print_lmem(9)xe_gt_sriov_pf_config_print_available_ggtt(9)
okay that's the page!! sign-off time π«Ά this whole thing lives in ./drivers/gpu/drm/xe and it's dated October 2026, and the footer still says xe_gt_sriov_...antum_locked(9) because of course it does. go configure those quantums bestie, ily, drink water πβ¨πΈ
π¦ 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