xe_sriov_vfio_resume_device(9)

💖 xe_sriov_vfio_resume_device — the kernel API manual, bestie edition 💖

Okay so like, welcome to the <pink>xe_sriov_vfio_resume_device(9)</pink> page!! It lives in the <purple>Kernel API Manual</purple> (yes, that's the manual name, I'm folding it in right here at the top, you're welcome 🫶). This is the one that wakes your VF back up. Let's get into it ✨

---

🌸 NAME 🌸

xe_sriov_vfio_resume_device — Resume VF. That's literally it, that's the whole vibe check 💅

---

🦋 SYNOPSIS 🦋

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

---

🎀 ARGUMENTS 🎀

• xe — the PF xe_device, and the way you get your hands on it is by calling xe_sriov_vfio_get_pf. Iconic, no cap 💜
• vfid — the VF identifier. And bestie, heads up: it can't be 0 🚫🙈

---

✨ DESCRIPTION ✨

So this function? It resumes the VF on all tiles. All of them. Every single one. Main character energy across the whole board 👑🔥

---

⭐ RETURN ⭐

• 0 on success 🥳
• a negative error code on failure 😭 (which, as always, is not the vibe)

---

🌈 SEE ALSO 🌈

Kernel file ./include/drm/intel/xe_sriov_vfio.h, plus the whole friend group:

• 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_stop_copy_enter(9)
• xe_sriov_vfio_stop_copy_exit(9)
• xe_sriov_vfio_resume_data_enter(9)
• xe_sriov_vfio_resume_data_exit(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)

---

🧚 And that's the whole page, bestie! Sending you off with the softest sign-off ever: this one comes from <lavender>./include/drm/intel</lavender>, dated <cyan>October 2026</cyan>, and it's forever filed under <hotpink>xe_sriov_vfio_resume_device(9)</hotpink>. Slay, go resume that VF 💅💖🔥