xe_sriov_pf_...nish_save_vf(9)

💅 xe_sriov_pf_...nish_save_vf(9) 💅

okay so bestie, welcome to the Kernel API Manual — yes that's the vibe, we're reading kernel docs together and honestly? iconic. this page is about xe_sriov_pf_...nish_save_vf(9) (the title got cut off mid-word and honestly same, but the full name is right below, don't panic 🫶).

---

✨ NAME ✨

xe_sriov_pf_control_finish_save_vf — it completes the VF migration data SAVE sequence, and it does it across all GTs. that's the whole job. no cap. 🎀

---

🌸 SYNOPSIS 🌸

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

literally that's the call. copy it exactly, i'm not joking about the spacing, kernel devs notice everything 😭

---

🦋 ARGUMENTS 🦋

• xe — your xe_device. the big one. the main character, honestly 👑
• vfid — the VF identifier. it's an unsigned int, and it's how you tell it which virtual function we're talking about 💫

---

💜 DESCRIPTION 💜

so this function is for PF only. that's it. that's the whole description. PF only, bestie — like, don't come at it as a VF, it will not answer the phone 🙈

ngl the original docs are kinda short here, and i'm not about to invent lore. PF only. periodt.

---

⭐ RETURN ⭐

• 0 on success 🎉 slay
• a negative error code on failure 💀 (not zero, not positive — negative. remember that.)

---

🌈 SEE ALSO 🌈

the kernel file we live in:

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

and the whole friend group, 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_trigger_restore_vf(9)
• xe_sriov_pf_control_finish_restore_vf(9)

---

okay that's the page!! sourced straight from ./drivers/gpu/drm/xe, dated October 2026, and honestly you ate that reading session. go forth and finish those saves 🧚💖 bye bestie!! 💅✨