xe_gt_sriov...ig_print_dbs(9)
π xe_gt_sriov_pf_config_print_dbs β Print GuC doorbell ID configurations π
okay so bestie, welcome to the Kernel API Manual β¨ (yes, that's the manual name, and yes, the header up top is the truncated lil version of the title β xe_gt_sriov...ig_print_dbs(9) β you're in the right place, don't panic π«Ά). This is the page you want if you're messing with SR-IOV PF config printing. Buckle up, it's short and sweet.
πΈ NAME πΈ
xe_gt_sriov_pf_config_print_dbs β Print GuC doorbell ID configurations.
π« SYNOPSIS π«
int xe_gt_sriov_pf_config_print_dbs (struct xe_gt *gt , struct
drm_printer *p );
π ARGUMENTS π
gtβ thexe_gtπ (your graphics tile, the main character here)pβ thedrm_printerπ¨οΈ (the thing that actually does the printing, obvs)
β¨ DESCRIPTION β¨
So what does this bad boy do? It prints GuC doorbell ID allocations across all VFs. That's it, that's the job π .
And here's a lil detail that's lowkey important: VFs that don't have GuC doorbell IDs? They get skipped. Not me ghosting them β the function does it fr fr π.
β οΈ Heads up bestie: This function can only be called on PF. That's not a suggestion, that's the rule. Don't come crying to me if you try it on a VF π
π RETURN π
- Returns
0on success π - or a negative error code on failure π
That's the whole vibe check β zero means slay, negative means nope.
π¦ SEE ALSO π¦
Kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c β go read it, it's giving main character energy π
And literally the whole friend group of related functions, 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_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_lmem(9)xe_gt_sriov_pf_config_print_available_ggtt(9)
πΈ okay that's the whole page, you ate that πΈ This one lives under ./drivers/gpu/drm/xe, dated October 2026 β love that for us. Now go print some doorbell IDs, bestie πππ¦
π¦ 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