xe_gsc_poison_header(9)

💅 xe_gsc_poison_header(9) — the Kernel API Manual, bestie edition 🎀

okay so real talk, this is a page from the Kernel API Manual and honestly? it's a whole vibe. we're talking xe_gsc_poison_header — the function that goes and poisons the MTL GSC header sitting in memory. yes, poison. dramatic? maybe. necessary? absolutely. ✨

---

🌸 NAME 🌸

xe_gsc_poison_header — poison the MTL GSC header in memory 💀

like, literally that's the job. it takes a header in memory and makes it ~poisoned~. no cap.

---

🦋 SYNOPSIS 🦋

void xe_gsc_poison_header (struct xe_device *xe , struct iosys_map *map
, u32 offset );

that's the whole signature, copy it exactly bestie, don't get creative with it 🙈

---

✨ ARGUMENTS ✨

three of them. not two, not four. three. let's go:

• xe — the Xe device 🖥️ like, the actual device we're doing this to.
• map — the iosys map to write to ✍️ this is where the writing happens.
• offset — offset from the start of the map at which the header resides 📍 so like, where in the map the header is chilling.

---

👑 SEE ALSO 👑

go look at the actual kernel file, it's right here:

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

and the whole friend group of related functions:

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

they all live in the same orbit, iykyk 🌈

---

ngl the whole point is in the name — this one poisons the MTL GSC header in memory. don't overthink it, just let it slay 🫶

---

and that's the page!! 🎀 source path is ./drivers/gpu/drm/xe, dated October 2026, and the function is xe_gsc_poison_header(9) — periodt. go poison that header bestie, you got this 💖✨