xe_gsc_read_out_header(9)

💅 xe_gsc_read_out_header — kernel API manual, bestie edition ✨

okay so real talk: this one lives in the Kernel API Manual, and honestly? it's giving "tiny function, big responsibilities." 🎀 It reads the output header, validates it, and hands you back the offset of the reply that comes right after the header. Lowkey iconic. No cap. 👑

---

✨ NAME ✨

xe_gsc_read_out_header — reads and validates the output header and returns the offset of the reply following the header 🦋

---

🌸 SYNOPSIS 🌸

int xe_gsc_read_out_header (struct xe_device *xe , struct iosys_map *map
, u32 offset , u32 min_payload_size , u32 *payload_offset );

like, that's the whole signature, copied exactly, don't come for me 💅

---

💖 ARGUMENTS 💖

• xe — the Xe device, the main character of this whole operation 👑
• map — the iosys map that's holding your output buffer
• offset — where inside the iosys your output buffer is actually sitting
• min_payload_size — the minimum size of the message, not counting the gsc header
• payload_offset — an optional pointer, and if you pass it, it gets set to the payload offset ✨

ok bestie, note that payload_offset is optional. you don't have to hand it over. it's not that kind of function. 🫶

---

🌈 RETURN 🌈

An -errno value if things go wrong, and 0 otherwise. that's it, that's the vibe check ✅

---

🧚 SEE ALSO 🧚

Kernel file:

./drivers/gpu/drm/xe/xe_gsc_submit.c

and the rest of the friend group 💜:

• xe_gsc_create_host_session_id(9)
• xe_gsc_emit_header(9)
• xe_gsc_poison_header(9)
• xe_gsc_check_and_update_pending(9)
• xe_gsc_pkt_submit_kernel(9)

---

and that's the page, periodt. 💅 this little beauty comes from the ./drivers/gpu/drm/xe source, dated October 2026, fr fr — go off, Xe directory, you ate. 🔥🌷