xe_gt_sriov_..._prepare_flr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_gt_sriov_..._prepare_flr(9) β€” from the Kernel API Manual, bestie

okay so picture this: it's a whole Kernel API Manual page, the title is xe_gt_sriov_..._prepare_flr(9) (yes the abbreviation with the dots is literally part of the name, we don't question it), and it's all about one little function that does one very specific thing. let's get into it ✨


πŸŽ€ NAME πŸŽ€

xe_gt_sriov_pf_control_prepare_flr β€” the function that tells the PF "hey girl, a VF FLR request just got issued" πŸ‘€


✨ SYNOPSIS ✨

int xe_gt_sriov_pf_control_prepare_flr (struct xe_gt *gt , unsigned int vfid );

like, that's the whole signature. short and iconic. πŸ’…


🌸 ARGUMENTS 🌸

  • gt β€” the xe_gt. that's it, that's the description. the graphics tile in question 🫢
  • vfid β€” the VF identifier. which virtual function we're talking about, bestie πŸ”’

πŸ’– DESCRIPTION πŸ’–

so this is an optional early notification path, and its whole job is to mark a pending FLR before the GuC notifies the PF with a FLR event. think of it as the little heads-up text before the actual heads-up 😭

heads up! this function is for PF only. PF gang only. not VF. don't come in here if you're a VF πŸ™ˆ

πŸ”₯ RETURN πŸ”₯

  • 0 on success πŸŽ‰
  • a negative error code on failure πŸ’€

that's it. that's the whole return contract. no cap.


πŸ¦‹ SEE ALSO πŸ¦‹

okay this list is long, so buckle up bestie, we're going on a tour of every related state machine and function. no skipping, every single one makes the list πŸ‘‘

like I said. a lot. but we read them all, and honestly? kind of obsessed with how thorough this is 🌈


and that's the page, bestie! πŸ’œ this little gem lives under ./drivers/gpu/drm/xe in the Kernel API Manual, stamped October 2026 β€” go read the whole FLR state machine, it ate. periodt. πŸŽ€βœ¨

πŸ“¦ where this page comes from