xe_sriov_pf...gger_save_vf(9)

✨ NAME ✨

xe_sriov_pf_control_trigger_save_vf — okay bestie, this one kicks off the VF migration data SAVE sequence on all GTs. like, every single one. 💅

(it lives in the Kernel API Manual, in case the header didn't already scream that at you 🫶)

---

✨ SYNOPSIS ✨

int xe_sriov_pf_control_trigger_save_vf (struct xe_device *xe , unsigned
int vfid );

🌸 ARGUMENTS 🌸

• xe — the xe_device 💖 the actual graphics device struct, the main character of this whole operation.
• vfid — the VF identifier 🔥 which virtual function we're doing this for, k? k.

---

🦋 DESCRIPTION 🦋

So here's the tea: this function is for PF only. 🎀 PF as in physical function, and that's it — not VF, not anybody else. It starts the VF migration data SAVE sequence on all GTs. no cap, all of them.

---

🎯 RETURN 🎯

• 0 on success ✨ slay, we love a zero.
• a negative error code on failure 😭 and that's the negative error code on failure, fr fr.

---

👑 SEE ALSO 👑

The kernel file this lives in — go read it, iykyk:

./drivers/gpu/drm/xe/xe_sriov_pf_control.c

And the whole squad of related functions, because you're gonna need them:

• xe_sriov_pf_control_pause_vf(9)
• xe_sriov_pf_control_resume_vf(9)
• xe_sriov_pf_control_stop_vf(9)
• xe_sriov_pf_control_reset_vf(9)
• xe_sriov_pf_control_prepare_flr(9)
• xe_sriov_pf_control_wait_flr(9)
• xe_sriov_pf_control_sync_flr(9)
• xe_sriov_pf_control_finish_save_vf(9)
• xe_sriov_pf_control_trigger_restore_vf(9)
• xe_sriov_pf_control_finish_restore_vf(9)

---

ok that's the whole page 💀 don't come for me, everything's here — every option, every arg, every return value. ate and left no crumbs 🍓

and that's a wrap, bestie! 🧚 this little gem is served up from ./drivers/gpu/drm/xe, dated October 2026, and it's the xe_sriov_pf...gger_save_vf(9) page — go forth and save those VFs 💜