xe_sriov_vfio_wait_flr_done(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_sriov_vfio_wait_flr_done(9) ✨

okay so this is a page from the Kernel API Manual — yes, the Kernel API Manual, we're fancy now — and it's all about one little function called xe_sriov_vfio_wait_flr_done. Buckle up bestie, it's actually simple 🎀

🌸 NAME 🌸

xe_sriov_vfio_wait_flr_done — wait for VF FLR completion</p> 💖

like, it waits. that's the whole vibe. it waits for the FLR to be done. periodt.

✨ SYNOPSIS ✨

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

so it hands back an int, takes a struct xe_device *xe, and an unsigned int vfid. that's it, that's the whole signature, no cap 🫶

🦋 ARGUMENTS 🦋

  • xe — the PF xe_device that you got by calling xe_sriov_vfio_get_pf. like, you can't just roll up with any old device, you gotta have gotten it that way, iykyk 👑
  • vfid — the VF identifier. and listen: it can't be 0. zero is simply not invited to this party 🙈

💜 DESCRIPTION 💜

so what does it actually do? it waits. it will wait until the VF FLR is processed by the PF on all tiles — yes, all of them, every single tile, no skipping — or until a timeout occurs, whichever comes first 😭

it's giving patient main character energy. it sits there. it waits. it does not rush. ⭐

ngl if the timeout hits before the FLR finishes, that's just how it goes — the function waits for either the completion or the timeout, and that's the deal 💀

🌈 RETURN 🌈

  • 0 on success 🎉 slay
  • a negative error code on failure 😭 not slay

🧚 SEE ALSO 🧚

Kernel file ./include/drm/intel/xe_sriov_vfio.h and honestly the whole friend group:

go read them, they're iconic too 💅✨

and that's the page!! 🍓 this lil number lives in ./include/drm/intel, dated October 2026, and it's the xe_sriov_vfio_wait_flr_done(9) page — mwah, love that for us 💖🎀🦋

📦 where this page comes from