xe_guc_exec_...apshot_print(9)

🌸 NAME 🌸

xe_guc_exec_queue_snapshot_print — bestie, it prints out a given GuC Engine snapshot. That's it. That's the whole vibe. 💅

---

✨ SYNOPSIS ✨

void xe_guc_exec_queue_snapshot_print (struct xe_guc_submit_exec_queue_snapshot *snapshot , struct drm_printer *p );

---

🎀 ARGUMENTS 🎀

• snapshot — the GuC Submit Engine snapshot object itself, like the actual lil' moment captured in time 📸
• p — the drm_printer where it will be printed out. That's where all the output goes, no cap.

---

💖 DESCRIPTION 💖

Okay so real talk: this function prints out a given GuC Submit Engine snapshot object. Iconic behavior honestly. You hand it the snapshot, you hand it a printer, and it does the thing — the way that it just works is so main character energy. ✨🦋

---

👑 SEE ALSO 👑

Kernel file ./drivers/gpu/drm/xe/xe_guc_submit.c — that's the home base, iykyk 🏠

• xe_guc_submit_init(9)
• Multi Queue Group GuC interface(9)
• xe_guc_submit_wedge(9)
• xe_guc_submit_pause(9)
• xe_guc_submit_pause_vf(9)
• xe_guc_submit_unpause_prepare_vf(9)
• xe_guc_submit_unpause(9)
• xe_guc_submit_unpause_vf(9)
• xe_guc_submit_pause_abort(9)
• xe_guc_exec_queue_cgp_sync_done_handler(9)
• xe_guc_exec_queue_snapshot_capture(9)
• xe_guc_exec_queue_snapshot_capture_delayed(9)
• xe_guc_exec_queue_snapshot_free(9)
• xe_guc_register_vf_exec_queue(9)
• xe_guc_submit_print(9)
• xe_guc_has_registered_mlrc_queues(9)
• xe_guc_contexts_hwsp_rebase(9)

---

fr fr go read those if you wanna understand the whole GuC snapshot situation, they're literally all connected 🫶

---

And that's a wrap bestie!! 🎀 This cutie lives in ./drivers/gpu/drm/xe, dated October 2026, and it's officially called xe_guc_exec_...apshot_print(9) — slay, periodt. 💜⭐