xe_sriov_vf...e_data_enter(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_sriov_vfio_resume_data_enter — bestie, let's talk about restoring VF migration data

okay so this is a page from the Kernel API Manual (yes, the actual manual section for kernel API stuff, we love a glow-up ✨) and it's all about xe_sriov_vfio_resume_data_enter, which lowkey kicks off a VF device migration data restore. main character energy fr fr 🎀

✨ NAME ✨

xe_sriov_vfio_resume_data_enter — initiate a VF device migration data restore 💖

like, that's literally the whole vibe: you're entering the restore phase for a VF's migration data. no cap.

🌸 SYNOPSIS 🌸

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

that's it, that's the signature, copy it exactly, don't @ me 🫶

🦋 ARGUMENTS 🦋

  • xe — the PF xe_device you got by calling xe_sriov_vfio_get_pf. like, you can't just show up with any random device, bestie, you gotta obtain it the right way first 💅
  • vfid — the VF identifier. and listen... it can't be 0 🙈 that's the rule, that's the vibe check, 0 is not invited to this party.

⭐ RETURN ⭐

  • 0 on success 🎉 slay, we love a zero
  • a negative error code on failure 😭 it's giving "something went wrong", as negative error codes do

👑 SEE ALSO 👑

the whole friend group, and honestly they're all iconic in their own way:

ngl, xe_sriov_vfio_resume_data_exit(9) is literally the sibling of this function — you enter, then you exit. balanced, as all things should be 🌈

anyway, that's the whole page, no filler, no fluff, we kept every single detail because that's just how we do it 💜

sign-off corner 🧚: this one lives in ./include/drm/intel, it's dated October 2026, and it's page xe_sriov_vf...e_data_enter(9) of the Kernel API Manual. mwah, go restore some data bestie 💅✨

📦 where this page comes from