xe_gt_sriov_...xec_quantums(9)
π xe_gt_sriov_...xec_quantums(9) π
Okay bestie, welcome to the Kernel API Manual page for xe_gt_sriov_...xec_quantums(9) β yes, the header title is doing a little abbreviated moment, but the full function name is right below and she is serving. π«Ά
β¨ NAME β¨
xe_gt_sriov_pf_config_set_groups_exec_quantums β configure PF/VF EQs for sched groups. Slay.
π οΈ SYNOPSIS π οΈ
int xe_gt_sriov_pf_config_set_groups_exec_quantums (struct xe_gt *gt ,
unsigned int vfid , u32 *exec_quantums , u32 count );
π ARGUMENTS π
gtβ thexe_gt. Exactly what it says on the tin, bestie.vfidβ the PF or VF identifier. It's giving "who is this for?" energy.exec_quantumsβ array of requested EQs in milliseconds (0is infinity). Yup, zero is infinity here, no cap. πcountβ number of entries in the array. Gotta tell her how many little EQs are in there. β¨
π DESCRIPTION π
Okay so big rule first: this function can only be called on PF. No VF shenanigans, periodt. π«
It will log the provisioned value or an error in case of the failure. So if it works, you get the cute little log; if it fails, the error is also getting logged. Very "not me being transparent" of it. π
π₯ RETURN π₯
0on success.- A negative error code on failure.
That's it. Iconic, concise, no notes. β¨
π SEE ALSO π
Kernel file: ./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
Cross-reference city, because she knows everybody:
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_bulk_set_exec_quantum_locked(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)
Cute little sign-off: this page comes from ./drivers/gpu/drm/xe, dated October 2026, and it's filed under xe_gt_sriov_...xec_quantums(9). Mwah πβ¨
π¦ 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