xe_gt_sriov_...fig_sanitize(9)
xe_gt_sriov_pf_config_sanitize(9) π
okay so this is a page straight out of the Kernel API Manual, bestie β the header even says xe_gt_sriov_...fig_sanitize(9) twice because it's that iconic β¨. Sit down, grab a strawberry drink π, and let's get into it.
πΈ NAME πΈ
xe_gt_sriov_pf_config_sanitize β literally just sanitizing a VF's resources, no cap π§Όβ¨
π¦ SYNOPSIS π¦
int xe_gt_sriov_pf_config_sanitize (struct xe_gt *gt , unsigned int vfid
, long timeout );
π ARGUMENTS π
gtβ thexe_gt, aka the graphics tile in question, the main character of the struct world πvfidβ the VF identifier. and listen, it can't be PF β that is not a vibe that is allowed here πtimeoutβ maximum timeout to wait for completion, measured in jiffies β³ (yes, jiffies, the kernel's cute little time unit)
π DESCRIPTION π
This function can only be called on PF. That's the whole bit. PF privileges only, bestie β no sneaking in π
β RETURN β
0on success π slay- a negative error code on failure π it's giving "something went wrong"
π₯ SEE ALSO π₯
the whole friend group, fr fr β first up, the source file itself:
- Kernel file
./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
and then the entire squad π«Ά:
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_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_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)
and that's the whole page, bestie π nothing skipped, nothing dropped. this little beauty lives over in ./drivers/gpu/drm/xe, it's dated October 2026, and it answers to the name xe_gt_sriov_...fig_sanitize(9) πβ¨ go be a PF about it π«Ά
π¦ 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