VF2GUC_RESFIX_START(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… VF2GUC_RESFIX_START

okay so this is a page out of the Kernel API Manual, and honestly? it's a whole little protocol moment. stay with me bestie, it's easier than it looks 🫢

✨ NAME ✨

VF2GUC_RESFIX_START β€” the vibe-check message a VF sends to the GuC to say "hey, the VF KMD is about to start its post-migration recovery fixups" 🌸


πŸ¦‹ DESCRIPTION πŸ¦‹

so basically, this action is what the VF uses to inform the GuC that the VF KMD is about to kick off its post-migration recovery fixups. main character announcement energy, fr fr.

⚠️ important: the MARKER you send along with this action must match the MARKER posted in the VF2GUC_RESFIX_DONE message. like, they have to match. no cap. if they don't, that's gonna be a problem πŸ’€

this message must be sent as an MMIO HXG Message.

available since GuC VF compatibility 1.27.0 ✨ (so yes, it's got lore)

πŸŽ€ the request bits (what you send) πŸŽ€

  • bit 31 β€” ORIGIN = GUC_HXG_ORIGIN_HOST_
  • bits 30:28 β€” TYPE = GUC_HXG_TYPE_REQUEST_
  • bits 27:16 β€” DATA0 = MARKER β€” and listen, it can't be zero. like, zero is not it πŸ™ˆ
  • bits 15:0 β€” ACTION = GUC_ACTION_VF2GUC_RESFIX_START = 0x550F

πŸ’– the response bits (what comes back) πŸ’–

  • bit 31 β€” ORIGIN = GUC_HXG_ORIGIN_GUC_
  • bits 30:28 β€” TYPE = GUC_HXG_TYPE_RESPONSE_SUCCESS_
  • bits 27:0 β€” DATA0 = MBZ

(MBZ = "must be zero", so if you were thinking of putting something cute in there… don't πŸ’…)


πŸ‘‘ SEE ALSO πŸ‘‘

kernel file: ./drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h

and the whole friend group 🫢


and that's the whole page, bestie ✨ this one lives down in ./drivers/gpu/drm/xe/abi, dated October 2026, and it's literally titled VF2GUC_RESFIX_START(9). periodt πŸ’…πŸ’–

πŸ“¦ where this page comes from