xe_sriov_vfi...me_data_exit(9)

💅 NAME 💅

Okay bestie, so this is a Kernel API Manual page — we're deep in xe_sriov_vfi...me_data_exit(9) territory — and the star of the show is xe_sriov_vfio_resume_data_exit, which literally finishes a VF device migration data restore. That's it, that's the whole vibe. ✨

---

🎀 SYNOPSIS 🎀

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

No cap, that's the whole signature. Copy it exactly, she's sensitive. 🫶

---

🌸 ARGUMENTS 🌸

• xe — the PF xe_device, and you get it by calling xe_sriov_vfio_get_pf. That's the only sanctioned way, iykyk.
• vfid — the VF identifier. And listen: it can't be 0. Like, genuinely cannot. Don't try it. 💀

---

⭐ RETURN ⭐

0 on success, or a negative error code on failure. That's the whole story — zero means slay, negative means something went sideways. 😭

---

🦋 SEE ALSO 🦋

This is the friend group, fr fr — the whole squad lives in the kernel file ./include/drm/intel/xe_sriov_vfio.h:

• xe_sriov_vfio_get_pf(9)
• xe_sriov_vfio_migration_supported(9)
• xe_sriov_vfio_flr_prepare(9)
• xe_sriov_vfio_wait_flr_done(9)
• xe_sriov_vfio_suspend_device(9)
• xe_sriov_vfio_resume_device(9)
• xe_sriov_vfio_stop_copy_enter(9)
• xe_sriov_vfio_stop_copy_exit(9)
• xe_sriov_vfio_resume_data_enter(9)
• xe_sriov_vfio_error(9)
• xe_sriov_vfio_data_read(9)
• xe_sriov_vfio_data_write(9)
• xe_sriov_vfio_stop_copy_size(9)

Go read them, they're all iconic in their own way. 👑

---

Alright bestie, that's the page 💖 — signed off from ./include/drm/intel, dated October 2026, and yes the footer still spells it xe_sriov_vfi...me_data_exit(9), we don't question the truncation, we simply respect it. 🌈