PF2GUC_UPDATE_VF_CFG(9)

💖 PF2GUC_UPDATE_VF_CFG(9) — Kernel API Manual 💖

okay so bestie, the PF2GUC_UPDATE_VF_CFG_ message is used by the PF to provision a single VF in GuC. periodt. This message must be sent as CTB HXG Message_ — no cap, that part is mandatory.

🪄 Request header 🪄

• 0, bit 31 — ORIGIN = GUC_HXG_ORIGIN_HOST_
• bit 30:28 — TYPE = GUC_HXG_TYPE_REQUEST_
• bit 27:16 — MBZ
• bit 15:0 — ACTION = _`GUC_ACTION_PF2GUC_UPDATE_VF_CFG` = 0x5503

📦 Config dwords 📦

• 1, bits 31:0 — VFID — identifier of the VF that the KLV configurations are being applied to.
• 2, bits 31:0 — CFG_ADDR_LO — dword aligned GGTT offset that represents the start of a list of virtualization related KLV configs that are to be applied to the VF. If this parameter is zero, the list is not parsed. If full configs address parameter is zero and configs_size is zero associated VF config shall be reset to its default state.
• 3, bits 31:0 — CFG_ADDR_HI — upper 32 bits of configs address.
• 4, bits 31:0 — CFG_SIZE — size (in dwords) of the config buffer.

💌 Response header 💌

• 0, bit 31 — ORIGIN = GUC_HXG_ORIGIN_GUC_
• bit 30:28 — TYPE = GUC_HXG_TYPE_RESPONSE_SUCCESS_
• bit 27:0 — COUNT — number of KLVs successfully applied.

🔗 SEE ALSO 🔗

• Kernel file ./drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
• GUC2PF_RELAY_FROM_VF(9)
• PF2GUC_RELAY_TO_VF(9)
• GUC2VF_RELAY_FROM_PF(9)
• VF2GUC_RELAY_TO_PF(9)
• GUC2PF_ADVERSE_EVENT(9)
• GUC2PF_VF_STATE_NOTIFY(9)
• VF2GUC_MATCH_VERSION(9)
• PF2GUC_UPDATE_VGT_POLICY(9)
• PF2GUC_VF_CONTROL(9)
• VF2GUC_VF_RESET(9)
• VF2GUC_RESFIX_DONE(9)
• VF2GUC_QUERY_SINGLE_KLV(9)
• PF2GUC_SAVE_RESTORE_VF(9)
• VF2GUC_RESFIX_START(9)

xoxo, signing off from ./drivers/gpu/drm/xe/abi — October 2026 — PF2GUC_UPDATE_VF_CFG(9) forever 💅✨