xe_gt_sriov...nish_save_vf(9)

✨ xe_gt_sriov_pf_control_finish_save_vf ✨

okay so bestie, welcome to the <pink>Kernel API Manual</pink> 💖 this one's a lil function with a very long name and honestly it's giving "i'm the last step of a saga" energy. it lives in section 9 of the manual, and yes we're gonna get through the whole thing together, no skipping 🫶

---

🌸 NAME 🌸

xe_gt_sriov_pf_control_finish_save_vf — complete a VF migration data save sequence 🎀

like, the final bow on the gift wrap. the "and that's a wrap" moment of the save flow. periodt. 💅

---

🦋 SYNOPSIS 🦋

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

that's the whole signature, character for character, no cap. it returns an int, takes a pointer to a struct xe_gt and an unsigned int for the VF id. 🧚

---

💜 ARGUMENTS 💜

• gt — the xe_gt 🌟 literally the graphics tile we're working with, that's the whole vibe.
• vfid — the VF identifier 🔥 which virtual function we're talking about, bestie. gotta know who we're finishing up for.

---

👑 DESCRIPTION 👑

so, what does it actually do? this function is for PF only. that's the physical function, the main character of this whole SR-IOV situation — not the VFs themselves, they don't get to call this one 💀

it's the one that completes a VF migration data save sequence, i.e. the closer, the "last one out, turn off the lights" of the save flow. iconic behavior honestly. ✨

ngl, "PF only" is a real boundary — don't go calling this from VF-land, it's not for you, and the manpage is very clear about that. 🙈

---

🌈 RETURN 🌈

• 0 — success, we ate, everything's good 🍓
• negative error code — failure 😭 something went sideways, and the negative number is your lil clue about what.

---

⭐ SEE ALSO ⭐

buckle up bestie, this list is long and every single one of them matters, so here we go, no skips 🎀

• Kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c — the source file, the origin story 💖
• The VF state machine(9)
• The VF PAUSE state machine(9)
• xe_gt_sriov_pf_control_pause_vf(9)
• The VF RESUME state machine(9)
• xe_gt_sriov_pf_control_resume_vf(9)
• The VF SAVE state machine(9)
• xe_gt_sriov_pf_control_check_save_data_done(9)
• xe_gt_sriov_pf_control_check_save_failed(9)
• xe_gt_sriov_pf_control_process_save_data(9)
• xe_gt_sriov_pf_control_trigger_save_vf(9)
• The VF RESTORE state machine(9)
• xe_gt_sriov_pf_control_check_restore_failed(9)
• xe_gt_sriov_pf_control_restore_data_done(9)
• xe_gt_sriov_pf_control_process_restore_data(9)
• xe_gt_sriov_pf_control_trigger_restore_vf(9)
• xe_gt_sriov_pf_control_finish_restore_vf(9)
• The VF STOP state machine(9)
• xe_gt_sriov_pf_control_stop_vf(9)
• The VF FLR state machine(9)
• xe_gt_sriov_pf_control_prepare_flr(9)
• xe_gt_sriov_pf_control_trigger_flr(9)
• xe_gt_sriov_pf_control_sync_flr(9)
• xe_gt_sriov_pf_control_wait_flr(9)
• The VF FLR Flow with GuC(9)
• xe_gt_sriov_pf_control_process_guc2pf(9)
• xe_gt_sriov_pf_control_init(9)
• xe_gt_sriov_pf_control_restart(9)

---

that's the whole page, bestie, every option, every reference, every last (9) 🫶

sign-off time: this page comes from ./drivers/gpu/drm/xe and it's dated October 2026 — so yeah, from the future, slay 💅🔮 hope this helped, ily, go read the state machine pages next 🎀✨