xe_gt_sriov...rol_wait_flr(9)
π xe_gt_sriov_pf_control_wait_flr β like, the whole vibe β¨
Okay bestie, so this page lives in the Kernel API Manual (yes, that manual, the one all the kernel girlies use), and it's all about one little function that literally just sits there and waits for a VF FLR to finish. Iconic. Lowkey underrated. Let's get into it π«Ά
πΈ NAME πΈ
xe_gt_sriov_pf_control_wait_flr β wait for a VF FLR to complete. That's it. That's the whole job. It waits. It completes. Slay.
β¨ SYNOPSIS β¨
int xe_gt_sriov_pf_control_wait_flr (struct xe_gt *gt , unsigned int
vfid );
So you hand it a gt and a vfid, and it gives you back an int. Simple. Clean. No cap π
π ARGUMENTS π
gtβ thexe_gt. Your graphics tile. Your main character. You know her, you love her π«vfidβ the VF identifier. Like a little name tag so the function knows which VF we're talking about. iykyk π·οΈ
π¦ DESCRIPTION π¦
So the one thing you literally cannot miss here: this function is for PF only. Periodt. Not VF. PF. If you're a VF bestie, this is not your moment, sorry not sorry π
For the PF girlies, though? It's giving "wait for a VF FLR to complete," and it does exactly what it says on the tin. No plot twists. No surprises. Just vibes and patience β³
π₯ RETURN π₯
0on success β we love a happy ending π- a negative error code on failure β and honestly? π at least it tells you
π SEE ALSO π
Okay this is the part where the manpage just goes off β the whole friend group is tagged, so let's name every single one, no skipping, because we don't do that here π
- Kernel file
./drivers/gpu/drm/xe/xe_gt_sriov_pf_control.cβ the literal home address π - The VF state machine(9)
- The VF PAUSE state machine(9)
xe_gt_sriov_pf_control_pause_vf(9)- The VF RESUME state machine(9)
xe_gt_sriov_pf_control_resume_vf(9)- The VF SAVE state machine(9)
xe_gt_sriov_pf_control_check_save_data_done(9)xe_gt_sriov_pf_control_check_save_failed(9)xe_gt_sriov_pf_control_process_save_data(9)xe_gt_sriov_pf_control_trigger_save_vf(9)xe_gt_sriov_pf_control_finish_save_vf(9)- The VF RESTORE state machine(9)
xe_gt_sriov_pf_control_check_restore_failed(9)xe_gt_sriov_pf_control_restore_data_done(9)xe_gt_sriov_pf_control_process_restore_data(9)xe_gt_sriov_pf_control_trigger_restore_vf(9)xe_gt_sriov_pf_control_finish_restore_vf(9)- The VF STOP state machine(9)
xe_gt_sriov_pf_control_stop_vf(9)- The VF FLR state machine(9)
xe_gt_sriov_pf_control_prepare_flr(9)xe_gt_sriov_pf_control_trigger_flr(9)xe_gt_sriov_pf_control_sync_flr(9)- The VF FLR Flow with GuC(9)
xe_gt_sriov_pf_control_process_guc2pf(9)xe_gt_sriov_pf_control_init(9)xe_gt_sriov_pf_control_restart(9)
Like, the whole FLR friend group showed up to the group chat. We love a supportive cast π
Ngl, if you're a VF reading this hoping for a little something β this page isn't for you. PF only. That's the rule. π
Okay that's the whole page bestie, hope it ate ππ Mwah! This lil' beauty comes from ./drivers/gpu/drm/xe and it's dated October 2026 β mark your calendars, the future is now, and the manual name is still xe_gt_sriov...rol_wait_flr(9) in case you forgot β¨π§ββοΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms