xe_gsc_chec...date_pending(9)

✨ NAME ✨

Okay bestie, so this one's xe_gsc_check_and_update_pending(9) from the Kernel API Manual — and what it does is literally in the name: it checks the pending bit, and then it updates the input header with the retry handle from the output header. That's the whole vibe. 🌸

---

🦋 SYNOPSIS 🦋

bool xe_gsc_check_and_update_pending (struct xe_device *xe , struct
       iosys_map *in , u32 offset_in , struct iosys_map *out , u32 offset_out
       );

It hands you back a bool, no cap. 💅

---

🎀 ARGUMENTS 🎀

Girl, there are five of them, and every single one matters, so let's go:

• xe — the Xe device itself. The main character, honestly. 👑
• in — the iosys map that's holding your input buffer.
• offset_in — the offset inside that iosys where the input buffer is chilling.
• out — the iosys map holding your output buffer.
• offset_out — the offset inside that iosys where the output buffer lives.

---

⭐ RETURN ⭐

• true — the pending bit was set, slay. 🔥
• false — it wasn't. That's it, that's the answer. 🫶

---

💖 SEE ALSO 💖

Like, go read the actual source if you wanna be nosy (respectfully):

• Kernel file ./drivers/gpu/drm/xe/xe_gsc_submit.c
• xe_gsc_create_host_session_id(9)
• xe_gsc_emit_header(9)
• xe_gsc_poison_header(9)
• xe_gsc_read_out_header(9)
• xe_gsc_pkt_submit_kernel(9)

---

And that's the whole page, bestie! 🧚 This lil icon comes courtesy of ./drivers/gpu/drm/xe, dated October 2026, and it's filed under xe_gsc_chec...date_pending(9) — yes the name is truncated, no we're not fixing it, it's iconic that way. 💜✨