xe_sriov_vf...p_copy_enter(9)

✨ NAME ✨

xe_sriov_vfio_stop_copy_enter — bestie, this is the one that kicks off a VF device migration data save 💾✨ (like, it's the opening act, the main character entrance of the migration flow, and I'm obsessed)

This one lives in the Kernel API Manual, so yeah, it's giving kernel-level realness 🎀

✨ SYNOPSIS ✨

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

🌸 ARGUMENTS 🌸

• xe — the PF xe_device, and no you can't just vibe your way into one of these, you get it by calling xe_sriov_vfio_get_pf 🫶
• vfid — the VF identifier, and heads up: it can't be 0 💀 like, zero is simply not it

💖 RETURN 💖

Returns 0 on success, or a negative error code on failure — so if you get a negative back, something did not slay, sorry 😭

🦋 SEE ALSO 🦋

The kernel file is ./include/drm/intel/xe_sriov_vfio.h and here's the whole friend group, all of them, no cap 👑

• 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_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)

okay that's the whole page, mwah 💅 this lil doc came from ./include/drm/intel and it's dated October 2026 — yeah, future girlie behavior fr fr ⭐🦋💜