xe_gt_sriov...nfig_release(9)
π
xe_gt_sriov_pf_config_release β NAME β¨
okay so this is xe_gt_sriov_pf_config_release π β the function that releases and resets VF configuration. that's it, that's the whole vibe. and yes bestie, it's a Kernel API Manual entry, we're in the big leagues now π
πΈ SYNOPSIS πΈ
int xe_gt_sriov_pf_config_release (struct xe_gt *gt , unsigned int vfid
, bool force );
literally just three things and a dream, no cap π«Ά
π ARGUMENTS π
gtβ thexe_gtπ the graphics tile in question, main character energy frvfidβ the VF identifier (can't be PF) π« like, it literally cannot be the PF, don't try itforceβ force configuration release π yep, it's one of those flags
π¦ DESCRIPTION π¦
lowkey important: this function can only be called on PF. π not VF, PF. if you're sitting there calling it on a VF, bestie... no. the vibe check failed. π
β RETURN β
0 on success π or a negative error code on failure π β that's the whole deal, iykyk.
π SEE ALSO π
first up, the source file itself if you wanna go read the real thing:
- Kernel file
./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.cπ
and now the whole extended friend group π (every single one, i did not skip a single one, you're welcome):
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_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)
π«Ά ok that's the whole page, nothing skipped, every flag accounted for. go release that config bestie π
and finally, the cute sign-off: this one lives in ./drivers/gpu/drm/xe π‘ and it's dated October 2026 β β see you then, 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