xe_sriov_pf_...r_restore_vf(9)

💅 xe_sriov_pf_control_trigger_restore_vf(9) 💅

okay so bestie, we're in the Kernel API Manual today — yes, the whole manual, and yes the page header up top is literally xe_sriov_pf_...r_restore_vf(9) because it got truncated by the vibes (and by the column width, honestly). the full, un-abbreviated name of the function is the star of the show below. let's get into it 🫶

---

✨ NAME ✨

xe_sriov_pf_control_trigger_restore_vf — it starts the VF migration data RESTORE sequence on all GTs. like, all of them. every GT. no cap 🦋

---

🌸 SYNOPSIS 🌸

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

---

🎀 ARGUMENTS 🎀

• xe — the xe_device. that's the device, bestie, the whole thing 💖
• vfid — the VF identifier. which VF are we talking about? this number says it 🧚

---

💜 DESCRIPTION 💜

so here's the tea: this function is for PF only. that's it, that's the whole description, and honestly she said what she said 👑

not me being the shortest DESCRIPTION section in the whole manual — periodt, the source said it and I'm not adding lore that isn't there 🙈

---

⭐ RETURN ⭐

• 0 — success, slay, we ate 💅
• a negative error code — failure, and we're sad about it 😭

---

🌈 SEE ALSO 🌈

the kernel file, right here in all her glory:

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

and the whole friend group, in order, no skipping:

• 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_finish_restore_vf(9)

iykyk, that's the whole control squad 🔥

---

okay that's the page!! sourced from ./drivers/gpu/drm/xe, dated October 2026, and filed under xe_sriov_pf_...r_restore_vf(9) (yes, still abbreviated, still iconic) — bye bestie, go restore some VF data 💖✨🎀