ENUM XE_GT_SRIOV_CONTROL_BITS(9)

💅 NAME 💅

enum xe_gt_sriov_control_bits — okay so this is the enum of various bits used by the PF to represent a VF state, and honestly it's giving state-machine royalty 👑 (and yes bestie, this is straight out of the kernel API manual, we're in the big leagues now)

✨ SYNOPSIS ✨

enum xe_gt_sriov_control_bits {
    XE_GT_SRIOV_STATE_WIP ,
    XE_GT_SRIOV_STATE_FLR_WIP ,
    XE_GT_SRIOV_STATE_FLR_PREPARE ,
    XE_GT_SRIOV_STATE_FLR_SEND_START ,
    XE_GT_SRIOV_STATE_FLR_WAIT_GUC ,
    XE_GT_SRIOV_STATE_FLR_GUC_DONE ,
    XE_GT_SRIOV_STATE_FLR_SYNC ,
    XE_GT_SRIOV_STATE_FLR_RESET_CONFIG ,
    XE_GT_SRIOV_STATE_FLR_RESET_DATA ,
    XE_GT_SRIOV_STATE_FLR_RESET_MMIO ,
    XE_GT_SRIOV_STATE_FLR_SEND_FINISH ,
    XE_GT_SRIOV_STATE_FLR_FAILED ,
    XE_GT_SRIOV_STATE_PAUSE_WIP ,
    XE_GT_SRIOV_STATE_PAUSE_SEND_PAUSE ,
    XE_GT_SRIOV_STATE_PAUSE_WAIT_GUC ,
    XE_GT_SRIOV_STATE_PAUSE_GUC_DONE ,
    XE_GT_SRIOV_STATE_PAUSE_FAILED ,
    XE_GT_SRIOV_STATE_PAUSED ,
    XE_GT_SRIOV_STATE_SAVE_WIP ,
    XE_GT_SRIOV_STATE_SAVE_PROCESS_DATA ,
    XE_GT_SRIOV_STATE_SAVE_WAIT_DATA ,
    XE_GT_SRIOV_STATE_SAVE_DATA_DONE ,
    XE_GT_SRIOV_STATE_SAVE_FAILED ,
    XE_GT_SRIOV_STATE_SAVED ,
    XE_GT_SRIOV_STATE_RESTORE_WIP ,
    XE_GT_SRIOV_STATE_RESTORE_PROCESS_DATA ,
    XE_GT_SRIOV_STATE_RESTORE_WAIT_DATA ,
    XE_GT_SRIOV_STATE_RESTORE_DATA_DONE ,
    XE_GT_SRIOV_STATE_RESTORE_FAILED ,
    XE_GT_SRIOV_STATE_RESTORED ,
    XE_GT_SRIOV_STATE_RESUME_WIP ,
    XE_GT_SRIOV_STATE_RESUME_SEND_RESUME ,
    XE_GT_SRIOV_STATE_RESUME_FAILED ,
    XE_GT_SRIOV_STATE_RESUMED ,
    XE_GT_SRIOV_STATE_STOP_WIP ,
    XE_GT_SRIOV_STATE_STOP_SEND_STOP ,
    XE_GT_SRIOV_STATE_STOP_FAILED ,
    XE_GT_SRIOV_STATE_STOPPED ,
    XE_GT_SRIOV_STATE_MISMATCH

};

🎀 Constants 🎀

Okay so like, here's every single member and what it's actually saying, no cap 🫶

• XE_GT_SRIOV_STATE_WIP — the "not me but also yes me" bit 💀 — indicates that some operations are in progress.
• XE_GT_SRIOV_STATE_FLR_WIP — indicates that a VF FLR is in progress.
• XE_GT_SRIOV_STATE_FLR_PREPARE — indicates that the PF received early VF FLR prepare notification.
• XE_GT_SRIOV_STATE_FLR_SEND_START — indicates that the PF wants to send a FLR START command.
• XE_GT_SRIOV_STATE_FLR_WAIT_GUC — indicates that the PF awaits for a response from the GuC.
• XE_GT_SRIOV_STATE_FLR_GUC_DONE — indicates that the PF has received a response from the GuC.
• XE_GT_SRIOV_STATE_FLR_SYNC — indicates that the PF awaits to synchronize with other GuCs.
• XE_GT_SRIOV_STATE_FLR_RESET_CONFIG — indicates that the PF needs to clear VF's resources.
• XE_GT_SRIOV_STATE_FLR_RESET_DATA — indicates that the PF needs to clear VF's data.
• XE_GT_SRIOV_STATE_FLR_RESET_MMIO — indicates that the PF needs to reset VF's registers.
• XE_GT_SRIOV_STATE_FLR_SEND_FINISH — indicates that the PF wants to send a FLR FINISH message.
• XE_GT_SRIOV_STATE_FLR_FAILED — indicates that VF FLR sequence failed 😭
• XE_GT_SRIOV_STATE_PAUSE_WIP — indicates that a VF pause operation is in progress.
• XE_GT_SRIOV_STATE_PAUSE_SEND_PAUSE — indicates that the PF is about to send a PAUSE command.
• XE_GT_SRIOV_STATE_PAUSE_WAIT_GUC — indicates that the PF awaits for a response from the GuC.
• XE_GT_SRIOV_STATE_PAUSE_GUC_DONE — indicates that the PF has received a response from the GuC.
• XE_GT_SRIOV_STATE_PAUSE_FAILED — indicates that a VF pause operation has failed.
• XE_GT_SRIOV_STATE_PAUSED — indicates that the VF is paused. holding still, main character freeze-frame ✋
• XE_GT_SRIOV_STATE_SAVE_WIP — indicates that VF save operation is in progress.
• XE_GT_SRIOV_STATE_SAVE_PROCESS_DATA — indicates that VF migration data is being produced.
• XE_GT_SRIOV_STATE_SAVE_WAIT_DATA — indicates that PF awaits for space in migration data ring.
• XE_GT_SRIOV_STATE_SAVE_DATA_DONE — indicates that all migration data was produced by Xe.
• XE_GT_SRIOV_STATE_SAVE_FAILED — indicates that VF save operation has failed.
• XE_GT_SRIOV_STATE_SAVED — indicates that VF data is saved. it's locked in, periodt 💾
• XE_GT_SRIOV_STATE_RESTORE_WIP — indicates that VF restore operation is in progress.
• XE_GT_SRIOV_STATE_RESTORE_PROCESS_DATA — indicates that VF migration data is being consumed.
• XE_GT_SRIOV_STATE_RESTORE_WAIT_DATA — indicates that PF awaits for data in migration data ring.
• XE_GT_SRIOV_STATE_RESTORE_DATA_DONE — indicates that all migration data was produced by the user.
• XE_GT_SRIOV_STATE_RESTORE_FAILED — indicates that VF restore operation has failed.
• XE_GT_SRIOV_STATE_RESTORED — indicates that VF data is restored.
• XE_GT_SRIOV_STATE_RESUME_WIP — indicates that a VF resume operation is in progress.
• XE_GT_SRIOV_STATE_RESUME_SEND_RESUME — indicates that the PF is about to send RESUME command.
• XE_GT_SRIOV_STATE_RESUME_FAILED — indicates that a VF resume operation has failed.
• XE_GT_SRIOV_STATE_RESUMED — indicates that the VF was resumed.
• XE_GT_SRIOV_STATE_STOP_WIP — indicates that a VF stop operation is in progress.
• XE_GT_SRIOV_STATE_STOP_SEND_STOP — indicates that the PF wants to send a STOP command.
• XE_GT_SRIOV_STATE_STOP_FAILED — indicates that the VF stop operation has failed 💀
• XE_GT_SRIOV_STATE_STOPPED — indicates that the VF was stopped.
• XE_GT_SRIOV_STATE_MISMATCH — indicates that the PF has detected a VF state mismatch. 🚨 the vibes do NOT align, bestie

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_pf_control_types.h
• struct xe_gt_sriov_control_state(9)
• struct xe_gt_sriov_pf_control(9)

go read those too, iykyk 🦋

ok so that's the whole page, no crumbs left behind, fr fr 🍓

kisses bestie, this one's straight out of ./drivers/gpu/drm/xe, dated October 2026 — slay 💖✨🎀