xe_gt_sriov_pf_monitor_flr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_gt_sriov_pf_monitor_flr β€” Kernel API Manual ✨

okay so bestie, welcome to the function page for xe_gt_sriov_pf_monitor_flr(9). yes the name is a whole mouthful, no we're not changing it, it's iconic in a chaotic way. let's get into it 🫢


🌸 NAME 🌸

xe_gt_sriov_pf_monitor_flr β€” cleanup VF data after VF FLR. that's the whole vibe. it tidies up. it's giving "mom coming home and the party's over" energy 🧹✨


⭐ SYNOPSIS ⭐

void xe_gt_sriov_pf_monitor_flr(struct xe_gt *gt, u32 vfid);

returns nothing (void, so don't go trying to catch a return value, there isn't one, periodt) πŸ’€


πŸŽ€ ARGUMENTS πŸŽ€

  • gt β€” the xe_gt. that's the graphics tile situation, literally the main character of this whole call πŸ¦‹
  • vfid β€” the VF identifier. it's a u32, and it's how we know which virtual function we're talking about πŸ’–

πŸ”₯ DESCRIPTION πŸ”₯

so here's the tea: on FLR, this function will reset all event data related to the VF. all of it. wiped. fresh start, no cap 🌈

and this one is for PF only β€” like, only the Physical Function gets to call this. don't come at it from anywhere else, iykyk πŸ‘‘


πŸ‘‘ SEE ALSO πŸ‘‘


ngl bestie, if you got here it's probably because something FLR'd and you needed to know the cleanup story. you're doing great. drink some water. πŸ’œ

🌸 mwah, that's the page! brought to you by ./drivers/gpu/drm/xe, October 2026, and the letter xe_gt_sriov_pf_monitor_flr(9). slay, bye! πŸŽ€βœ¨

πŸ“¦ where this page comes from