xe_gt_sriov...nfig_restart(9)
π
xe_gt_sriov_pf_config_restart π
okay so bestie, we're in the Kernel API Manual today and this page is about xe_gt_sriov_pf_config_restart β yes the title is the long one with the ... in the middle, it's giving "my name got truncated by the tab bar" energy and honestly? iconic.
πΈ NAME πΈ
xe_gt_sriov_pf_config_restart β restart your SR-IOV configurations after a GT reset, no cap.
β¨ SYNOPSIS β¨
void xe_gt_sriov_pf_config_restart (struct xe_gt *gt );
returns nothing (void, she's just here to do the work πββοΈ) and takes exactly one thing.
π ARGUMENTS π
gtβ thexe_gt. that's it. that's the whole argument. she's literally the GT, the main character π
π¦ DESCRIPTION π¦
okay so picture this: when the GT gets reset, any prior configurations you pushed to GuC are gone. lost. evaporated. not me crying over orphaned config π
so what does this function do? it pushes all non-empty VF configurations to the GuC again. like a "hey girl, re-send that" text. everything that still had something in it gets re-pushed, and the empty ones get to sit this one out π«Ά
β οΈ also this function can only be called on PF. not VF. PF only. don't try it anywhere else, that's the rule and we respect the rule π§
π SEE ALSO π
the kernel file itself lives at ./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c β go say hi π
and here's the whole friend group, all of them, every single one, I'm not skipping a single bestie:
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_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_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)
like I said. the whole group chat. π
π and that's the page, bestie! this one ships from./drivers/gpu/drm/xe, dated October 2026, and it's filed underxe_gt_sriov...nfig_restart(9)β the truncated name that ate and left no crumbs. 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