xe_gt_sriov_pf_config_save(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’Ύ xe_gt_sriov_pf_config_save(9) β€” Kernel API Manual πŸ’Ύ

okay bestie, welcome to the Kernel API Manual page for xe_gt_sriov_pf_config_save(9). This one is giving β€œsave the VF provisioning config as a binary blob” energy, and we’re gonna get through every arg, return value, and reference without losing a single crumb. no cap. ✨


✨ NAME ✨

xe_gt_sriov_pf_config_save β€” Save a VF provisioning config as binary blob.

Like, it’s the save button for a VF provisioning config, but make it raw bytes, bestie. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

here’s the signature, character-for-character:

ssize_t xe_gt_sriov_pf_config_save (struct xe_gt *gt , unsigned int vfid
       , void *buf , size_t size );

πŸ’… ARGUMENTS πŸ’…

  • gt β€” the xe_gt. The GT object in question, front and center.
  • vfid β€” the VF identifier. can't be PF β€” the page is loud about that, so don’t try it. 🫢
  • buf β€” the buffer to save a config to, or NULL if you’re querying the buf size.
  • size β€” the size of the buffer, or 0 if you’re querying the buf size.

πŸ¦‹ DESCRIPTION πŸ¦‹

This function can only be called on PF.

That’s the whole vibe check, bestie: PF only. If you’re not on PF, this function is not the move. periodt. πŸ¦‹


πŸ”₯ RETURN πŸ”₯

It returns the minimum size of the buffer, or the number of bytes saved, or a negative error code on failure. So you’re either getting size info, actual saved bytes, or a lil negative error telling you it didn’t slay. 😭


πŸ’œ SEE ALSO πŸ’œ

Kernel file: ./drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c

the whole friend group, all in (9):


cute lil sign-off: this page lives under source path ./drivers/gpu/drm/xe, dated October 2026, and it’s xe_gt_sriov_pf_config_save(9) β€” bye bestie! πŸ’–

πŸ“¦ where this page comes from