xe_sriov_vfio_flr_prepare(9)

💅 xe_sriov_vfio_flr_prepare(9) — like, the whole kernel API manual vibe 🎀

okay bestie so you're reading the Kernel API Manual page for xe_sriov_vfio_flr_prepare(9) and honestly? it's a little baddie of a function. let's get into it ✨

---

🌸 NAME 🌸

xe_sriov_vfio_flr_prepare — notify the PF that VF FLR prepare has started. that's it, that's the whole job 💅

---

✨ SYNOPSIS ✨

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

look at her go 🫶 one call, two args, int coming back at you.

---

🦋 ARGUMENTS 🦋

• xe — the PF xe_device, and you get it by calling xe_sriov_vfio_get_pf. that's the only way in, no cap 🔥
• vfid — the VF identifier. and bestie, listen: it can't be 0. zero is not invited to this party 🙈

---

💖 DESCRIPTION 💖

so what does she do? this function marks the VF FLR as pending before the PF receives the GuC FLR event. that's the whole tea ☕ the timing is literally the point — pending gets set first, GuC event comes after. iykyk 💀

---

🌈 RETURN 🌈

• 0 → slay, it worked, success 👑
• a negative error code → not slay, it failed 😭

---

🎀 SEE ALSO 🎀

the whole friend group, plus the kernel file they live in:

• Kernel file ./include/drm/intel/xe_sriov_vfio.h
• xe_sriov_vfio_get_pf(9)
• xe_sriov_vfio_migration_supported(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_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)

---

💜 friendly rememinder: vfid can't be 0. i said what i said.

---

mwah 💋 that's the page!! sourced from ./include/drm/intel, dated October 2026, and it's giving main character energy all the way through. go read some more manpages bestie, love u, bye 🧚‍♀️🌸