HXG EVENT(9)

💅 HXG Event (9) 💅

okay bestie, welcome to the HXG Event page — it lives in the Kernel API Manual and it's genuinely so much simpler than it looks, i promise 🫶

---

✨ NAME ✨

HXG Event — the little message that kicks off async stuff and then dips without waiting around 💨

---

🎀 DESCRIPTION 🎀

so like, the HXG Event message is the one you send when you wanna initiate asynchronous activity — the kind that doesn't involve immediate confirmation and doesn't involve data. it's giving "fire and forget", no cap. 🔥

the format of DATA0 and all the DATAn fields? yeah, that depends entirely on the ACTION code. iykyk. 🦋

here's the bit layout of the first word, bestie — memorise it, it's iconic:

• bits 0 through 31 — ORIGIN 👑
• bits 30:28 — TYPE = GUC_HXG_TYPE_EVENT_ ⭐
• bits 27:16 — DATA0 — event data (depends on ACTION)
• bits 15:0 — ACTION — event action code 🎀

---

🌸 the extra words (DATAn) 🌸

after that first word you get optional extra words, and each one is just 31:0:

• word 1, bits 31:0 — DATAn — optional event data (depends on ACTION) 💖
• …
• word n, bits 31:0 — DATAn — optional event data (depends on ACTION) 💖

so like, n of them, all 31:0, all optional, all chillin'. the way that ACTION decides everything is lowkey the main character energy of this whole page ngl 💅

reminder bestie: DATA0 and every DATAn field's format is not fixed — it's completely up to the ACTION code. don't assume, okay? 🙈

---

🔍 SEE ALSO 🔍

• Kernel file ./drivers/gpu/drm/xe/abi/guc_messages_abi.h
• HXG Message(9)
• HXG Request(9)
• HXG Fast Request(9)
• HXG Busy(9)
• HXG Retry(9)
• HXG Failure(9)
• HXG Response(9)

---

that's the whole vibe, bestie — go read those other HXG pages, they ate fr fr 🌈

🎀 sourced from ./drivers/gpu/drm/xe/abi, dated October 2026, and yes the page is literally called HXG Event(9) — mwah, slay, periodt 💋✨