xe_sriov_pf_unprovision_vfs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_sriov_pf_unprovision_vfs β€” Kernel API Manual πŸŽ€

okay so bestie, welcome to the group chat. this is the page for xe_sriov_pf_unprovision_vfs(9), straight out of the Kernel API Manual, and it's lowkey a whole mood: we're taking VFs back in auto-mode. let's get into it ✨


✨ NAME ✨

xe_sriov_pf_unprovision_vfs β€” Unprovision VFs in auto-mode. that's it, that's the vibe πŸ¦‹


🌸 SYNOPSIS 🌸

int xe_sriov_pf_unprovision_vfs (struct xe_device *xe , unsigned int
       num_vfs );

like, copy it exactly, no cap β€” those spaces and that line break are part of the fit πŸ’…


🫢 ARGUMENTS 🫢

  • xe β€” the PF xe_device. yes, the PF one, hold that thought πŸ‘‘
  • num_vfs β€” the number of VFs to unprovision. how many are we un-provisioning bestie πŸ”₯

πŸ’– DESCRIPTION πŸ’–

This function can only be called on PF.

that's the whole paragraph. it's giving "short but iconic" β€” no extra lore, no secret bonus behaviour, nothing. PF only, periodt πŸ’€


⭐ RETURN ⭐

0 on success or a negative error code on failure. that's the classic return arc, we love a consistent king πŸ™ˆπŸ§š


🌈 SEE ALSO 🌈

Kernel file:

./drivers/gpu/drm/xe/xe_sriov_pf_provision.c

and the whole friend group of related calls, all present and accounted for, no one left behind 🫢:


ngl bestie, if you're calling this anywhere that isn't a PF, you're doing too much. the page says PF only, and the page does not lie πŸ’…

k that's the whole page!! mwah πŸ’‹ sending you off with the receipts: source lives in ./drivers/gpu/drm/xe, dated October 2026, and the page itself is xe_sriov_pf_unprovision_vfs(9). slay, go unprovision responsibly πŸŽ€βœ¨

πŸ“¦ where this page comes from