xe_sriov_vfi...op_copy_exit(9)

๐Ÿ“ฆ version 7.3.1, in nixpkgs unstable

๐Ÿ’… xe_sriov_vfi...op_copy_exit(9) ๐Ÿ’…

okay so this is a page straight outta the Kernel API Manual, and bestie, it's giving "one tiny function that finishes a big job" energy. the star of the show? xe_sriov_vfio_stop_copy_exit โ€” it wraps up a VF device migration data save. like, the data's already copied, this is the mic-drop moment where you're done saving. periodt. โœจ


๐ŸŒธ NAME ๐ŸŒธ

xe_sriov_vfio_stop_copy_exit โ€” finish a VF device migration data save. that's it, that's the whole vibe. it's the "okay we're done here, bye ๐Ÿ‘‹" of migration data saving.


๐ŸŽ€ SYNOPSIS ๐ŸŽ€

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

like, that's the whole signature. two args, one int coming back at you. no cap. ๐Ÿ’–


๐Ÿฆ‹ ARGUMENTS ๐Ÿฆ‹

  • xe โ€” the PF xe_device, and you get it by calling xe_sriov_vfio_get_pf. that's literally where it comes from, don't just manifest one out of thin air, iykyk. ๐Ÿ”ฎ
  • vfid โ€” the VF identifier, and bestie listen: it can't be 0. like, zero is not the move here. fr fr. ๐Ÿ™ˆ

โญ RETURN โญ

0 on success, or a negative error code if it failed. so basically zero = slay, negative = something went sideways. check it, don't ignore it. ๐Ÿ’€


๐Ÿ‘‘ SEE ALSO ๐Ÿ‘‘

this is the friend group, and they all live in the kernel file ./include/drm/intel/xe_sriov_vfio.h:

like, read the whole squad. it's giving main character energy but the whole ensemble ate. ๐ŸŒˆ


and that's the page!! go finish that save bestie, you got this. ๐Ÿซถ

signed off from ./include/drm/intel โ€” October 2026 edition, mwah ๐Ÿ’‹๐Ÿงšโ€โ™€๏ธ

๐Ÿ“ฆ where this page comes from