xe_sriov_pf...h_restore_vf(9)

✨ xe_sriov_pf_control_finish_restore_vf — the glow-up finale of the VF restore saga ✨

okay so real talk, bestie — you're looking at xe_sriov_pf...h_restore_vf(9) from the Kernel API Manual, and it's genuinely one of those "last step of the quest" functions 🎀. Full name is xe_sriov_pf_control_finish_restore_vf, and it wraps up the VF migration data RESTORE sequence on all GTs. literally all of them 💅

🌸 SYNOPSIS 🌸

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

🦋 ARGUMENTS 🦋

• xe — the xe_device in question, your main character struct no cap 🫶
• vfid — the VF identifier, aka which virtual function we're talking about 🔥

💖 DESCRIPTION 💖

So this function is for PF only — like, PF as in Physical Function. If you're not the PF, this is not your moment, bestie, it's giving "wrong lane" energy 💀. But if you are the PF? Slay. This is the one that completes the VF migration data RESTORE sequence on all GTs. all of them. periodt 💅✨

⭐ RETURN ⭐

• 0 on success 🎉 — icon behavior, we love to see it
• a negative error code on failure 😭 — not the vibe, but at least you know

👑 SEE ALSO 👑

The source lives at — like, go read it, it's right there, iykyk:

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

and it's got a whole friend group of sibling functions, obsessed with this squad fr fr:

• 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_trigger_save_vf(9)
• xe_sriov_pf_control_finish_save_vf(9)
• xe_sriov_pf_control_trigger_restore_vf(9)

🌈 okay that's the whole page, and tysm for reading 🫶 this gem lives in ./drivers/gpu/drm/xe, dated October 2026 ⭐ — catch you in the next manpage, bestie 🎀💜