xe_sriov_pf_...rol_sync_flr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_sriov_pf_control_sync_flr(9) β€” like, the whole Kernel API Manual, but make it make sense 🫢

okay so bestie, welcome to the xe_sriov_pf_...rol_sync_flr(9) page β€” yes that's the truncated little nickname the kernel gave it, the full gorgeous name is xe_sriov_pf_control_sync_flr and we're gonna get into it πŸ’–


✨ NAME ✨

xe_sriov_pf_control_sync_flr β€” Synchronize a VF FLR between all GTs. πŸŒ€

that's it. that's the whole vibe. syncing the FLR across all the GTs, no cap.


🌸 SYNOPSIS 🌸

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

literally just call it like that, icon behavior, returns an int πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • xe β€” the xe_device πŸ’œ like, the device you're doing the thing on, bestie.
  • vfid β€” the VF identifier 🌈 which VF you're talking about, periodt.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so lowkey important: this function is for PF only. 🫢 not VF, PF. don't come in here with VF energy, it's giving wrong call site. iykyk.


⭐ RETURN ⭐

  • 0 on success ✨ slay, we love a clean zero.
  • a negative error code on failure 😭 it's giving "something went wrong," and you should probably look at that.

πŸ‘‘ SEE ALSO πŸ‘‘

bestie, the whole friend group 🫢 go read these too:


and that's the page!! πŸŽ€πŸ’… mwah.

sign-off szn: this little number lives under ./drivers/gpu/drm/xe, dated October 2026, and it answers to xe_sriov_pf_...rol_sync_flr(9) 🌸 thanks for reading bestie, go sync those FLRs πŸ¦‹βœ¨
πŸ“¦ where this page comes from