xe_gt_sriov_pf_config_push(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_gt_sriov_pf_config_push(9) β€” like, the whole Kernel API Manual vibe, bestie ✨

okay so this is a page straight out of the Kernel API Manual, and it's about one very specific little function: xe_gt_sriov_pf_config_push. it reprovisions a VF's configuration, no big deal, only kind of a big deal 🫢


🌸 NAME 🌸

xe_gt_sriov_pf_config_push β€” reprovision VF's configuration</p>, that's literally the whole assignment πŸ’…


✨ SYNOPSIS ✨

int xe_gt_sriov_pf_config_push (struct xe_gt *gt , unsigned int vfid ,
bool refresh );

πŸŽ€ ARGUMENTS πŸŽ€

  • gt β€” the xe_gt. that's the one, the icon, the struct itself πŸ‘‘
  • vfid β€” the VF identifier, and bestie listen: it can't be PF. like, don't even try it πŸ™ˆ
  • refresh β€” explicit refresh. that's the flag, that's what it does, that's the whole personality ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: this function can only be called on PF. that's it, that's the rule, respect it fr fr πŸ’€


🌈 RETURN 🌈

  • 0 on success πŸ’–
  • a negative error code on failure 😭

like yes queen, we love a clean return contract πŸ‘‘


πŸ’œ SEE ALSO πŸ’œ

first up, the kernel file itself, go read it, it's giving source of truth:

  • ./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c

and now, the group chat β€” every single one of these siblings, no cap, in order 🫢


πŸ’€ lowkey reminder: all of the above are (9) section manpage references, so man 9 them if you're lost, iykyk. and again β€” this push function is PF-only, no VF shenanigans. πŸ“

and that's the page!! mwah πŸ’‹ this one came from ./drivers/gpu/drm/xe and it's dated October 2026 β€” go off, kernel docs, periodt. πŸ§šβ€β™€οΈβ­πŸ’–

πŸ“¦ where this page comes from