HXG FAILURE(9)

💅 HXG FAILURE(9) 💅

okay bestie, welcome to the Kernel API Manual — this one's short but she's important, so pay attention 🫶

✨ HXG Failure ✨

so HXG Failure is literally the "oops" text 💀 — it's the message you send back as a reply to an HXG Request that couldn't be processed because something went wrong. like, the request showed up, the vibe check failed, and this is the polite little note you send back. no cap.

🎀 the bits, laid out 🎀

here's how the bits line up — yes we're doing bit fields, stay with me:

• Bits 0, length 31 — ORIGIN 🌸
• Bits 30:28 — TYPE = GUC_HXG_TYPE_RESPONSE_FAILURE 👑 (like, this is the literal type tag, do not touch)
• Bits 27:16 — HINT — additional error hint 🦋
• Bits 15:0 — ERROR — error/result code 😭

so yeah, the top chunk is ORIGIN, then the TYPE, then HINT and ERROR snuggled up in the low bits. iconic layout, honestly.

🌈 SEE ALSO 🌈

go read these next, i'm obsessed:

• the kernel file ./drivers/gpu/drm/xe/abi/guc_messages_abi.h 📁
• HXG Message(9)
• HXG Request(9)
• HXG Fast Request(9)
• HXG Event(9)
• HXG Busy(9)
• HXG Retry(9)
• HXG Response(9)

iykyk 💜

and that's the whole page, bestie — short and sweet, just like this one ⭐ this beauty lives at ./drivers/gpu/drm/xe/abi and it's dated October 2026, filed under HXG Failure(9). slay 💅✨