xe_gt_sriov_...fig_is_empty(9)
β¨ xe_gt_sriov_pf_config_is_empty β¨
okay so real talk, this is a page from the Kernel API Manual, section 9, and it's all about ONE tiny little boolean check. yes bestie, one bool. let's get into it π
πΈ NAME πΈ
xe_gt_sriov_pf_config_is_empty β literally just checks whether a VF's configuration is empty. that's the whole job. icon behavior tbh π
π¦ SYNOPSIS π¦
bool xe_gt_sriov_pf_config_is_empty (struct xe_gt *gt , unsigned int
vfid );
like, she takes two things and hands you back a bool. no cap, that's it π
π ARGUMENTS π
gtβ thexe_gtπ (yes, the whole gt struct, she's not picky)vfidβ the VF identifier. and listen: it can't be PF. like, that's not a vibe she supports, okay? π
π§ DESCRIPTION π§
This function can only be called on PF.
that's the entire description bestie π no extra lore, no secret sauce. PF only. periodt.
β RETURN β
returns true if the VF's mandatory configuration (GGTT, LMEM, ...) is empty π«Ά
so like... true = nothing set up yet, false = somebody's been decorating πΈ
π₯ SEE ALSO π₯
she lives in this file, for the record:
./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
and here's the whole friend group β every single one, no gatekeeping π
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_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 whole page, mwah π source situation is ./drivers/gpu/drm/xe, dated October 2026, and yes the title up top is the short little xe_gt_sriov_...fig_is_empty(9) because she's too iconic to spell out twice π«Άβ¨
π¦ 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