xe_gt_sriov...ig_print_dbs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 β€” the xe_gt πŸ‘‘ (your graphics tile, the main character here)
  • p β€” the drm_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 0 on 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:


🌸 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