xe_gt_sriov_...gger_save_vf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so this is xe_gt_sriov_pf_control_trigger_save_vf β€” it starts an SR-IOV VF migration data save sequence. like it kicks off the whole "save this VF's stuff" arc. main character energy, fr fr 🎬

This one lives in the Kernel API Manual (yes, the kernel has lore and this is part of it πŸ’…).


✨ SYNOPSIS ✨

int xe_gt_sriov_pf_control_trigger_save_vf(struct xe_gt *gt, unsigned int vfid);

πŸŽ€ ARGUMENTS πŸŽ€

  • gt β€” the xe_gt πŸš— (the graphics tile we're working with, bestie)
  • vfid β€” the VF identifier πŸ”’ (which virtual function we're talking about, iykyk)

🌸 DESCRIPTION 🌸

This function is for PF only. no cap β€” PF as in Physical Function, don't come at it as a VF, it's just not that girl for this call 🫢


⭐ RETURN ⭐

0 on success, or a negative error code on failure 😭 (so like, check the return value, please, I'm begging)


πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, honestly β€” go read these too:


ok that's the whole page!! go forth and trigger that save sequence responsibly, bestie πŸ¦‹

anyway, this fine piece of documentation comes straight out of ./drivers/gpu/drm/xe, dated October 2026 β€” slay, drop the date in the group chat, periodt πŸ‘‘πŸ’–

πŸ“¦ where this page comes from