xe_sriov_vfi...spend_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_sriov_vfi...spend_device(9) — the kernel API manual, but make it make sense

okay bestie, so this is a page from the Kernel API Manual — we're in the xe_sriov_vfi...spend_device(9) era (yes that's the truncated header, she's mysterious like that) and the actual star of the show is xe_sriov_vfio_suspend_device. Buckle up, we're going into VF suspend land 🦋

✨ NAME ✨

xe_sriov_vfio_suspend_device — literally just "suspend the VF." that's the whole vibe. 💤

🌸 SYNOPSIS 🌸

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

so she takes a struct xe_device * and an unsigned int, and she gives you back an int. simple queen behavior. no cap. 👑

🎀 ARGUMENTS 🎀

  • xe — the PF xe_device, and you only get one of these by calling xe_sriov_vfio_get_pf. like, that's the only way in, bestie. don't try to improvise 💅
  • vfid — the VF identifier. and listen, it can't be 0. that's the rule. zero is not invited to this party, periodt. 🙈

🔥 DESCRIPTION 🔥

this function will pause the VF on all tiles/GTs. all of them. every single one. it's giving "full stop, no exceptions." if you were wondering "does it pause just one tile?" — no ma'am, it's all of them. ✨

🌈 RETURN 🌈

  • 0 on success 💖
  • a negative error code on failure 😭

that's it. that's the return. keep it in mind, fr fr.

👑 SEE ALSO 👑

the kernel file ./include/drm/intel/xe_sriov_vfio.h and all her friends in the group chat:

go read them. iykyk 🧚

and that's the tea 🍓 this page lives in ./include/drm/intel, it's dated October 2026, and it's page xe_sriov_vfi...spend_device(9) of the Kernel API Manual. mwah, ily, go suspend some VFs responsibly 💜
📦 where this page comes from