THE VF STOP STATE MACHINE(9)

💅 The VF STOP state machine(9)

okay bestie, so this is a page from the Kernel API Manual, section 9 — yes, the real one, kernel docs, we're being ✨academic✨ today. And it's literally just about one thing: the VF STOP state machine. no cap.

🌀 the actual state machine

the page opens with the vibes, and the vibes are a diagram. it "looks like" this — and I'm putting it in a code block so the spacing doesn't get absolutely cooked, because the way that ASCII art is holding on by a thread is iconic honestly 💀:

       The VF STOP state machine looks like:

             (READY,PAUSED,RESUMED)<-------<--------------------o
                |                                                        stop                                                        |                                                       ....V..............................STOP_WIP......            :                                              :        o
            :        o----<----busy                        :        |
            :       /            /                         :        |
            :       STOP_SEND_STOP--------failed--->--------o--->(STOP_FAILED)
            :       /                                      :        |
            :    acked             rejected-------->--------o--->(MISMATCH)
            :     /                                         :
            :....o..............o...............o...........:
                 |              |               |
              completed        flr            restart
                 |              |               |
                 V         .....V.....          V
             (STOPPED)     : FLR_WIP :       (READY)
                           :.........:

like, look at it. we start chillin' in (READY,PAUSED,RESUMED), there's a stop path down into the STOP_WIP zone, busy loops back around, and then STOP_SEND_STOP branches off — acked goes one way, failed drops you into (STOP_FAILED), rejected sends you to (MISMATCH). and then out the bottom: completed → (STOPPED), flr → FLR_WIP, restart → right back to (READY). slay. 🎀

and if you're nosy and want the whole picture, the page says to check out The VF state machine_ for the full state machine view. iykyk 🦋

✨ SEE ALSO ✨

the whole group chat, in order, no one left out 🫶:

• kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
• 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)
• 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)
• xe_gt_sriov_pf_control_wait_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)

🌈 okay that's the whole page, you're officially educated. quick sign-off credits moment: this one's sourced from ./drivers/gpu/drm/xe, dated October 2026, and yes the title up top still says The VF STOP state machine(9) because we do not deadname a manpage. periodt. 💅👑