xe_guc_exec_...shot_capture(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_guc_exec_queue_snapshot_capture — the Kernel API Manual, bestie edition

okay so before we even start: this page lives in the Kernel API Manual, and the whole thing is about one function: xe_guc_exec_queue_snapshot_capture. Yes the title up top got squished into xe_guc_exec_...shot_capture(9) — that's just the header being dramatic and running out of room. The real name is the long one. 🎀

✨ NAME ✨

xe_guc_exec_queue_snapshot_capture — take a quick lil snapshot of the GuC Engine. like a selfie but for a faulty exec queue 📸✨

🦋 SYNOPSIS 🦋

struct xe_guc_submit_exec_queue_snapshot *
xe_guc_exec_queue_snapshot_capture (struct xe_exec_queue *q );

that's the whole vibe check right there, no cap.

🌸 ARGUMENTS 🌸

  • q — the faulty exec queue. the one that's misbehaving. the problem child. we're taking its picture for the record 🫶

💖 DESCRIPTION 💖

so the way this works is you grab the snapshot now, and it can be printed out at a later stage — like when you're doing dev_coredump analysis. think of it as saving the receipt so you can look at it later when everything's on fire 💀🔥

👑 RETURN 👑

you get back a GuC Submit Engine snapshot object. and listen — that thing must be freed by the caller using xe_guc_exec_queue_snapshot_free. no leaving it lying around, that's not main character energy, that's a leak. periodt.

🌈 SEE ALSO 🌈

k that's the whole page bestie, go read the others too, they're linked above and they ate 💅

okay and finally the sign-off: this iconic little page comes from the source path ./drivers/gpu/drm/xe, dated October 2026, and yeah — it goes by xe_guc_exec_...shot_capture(9) in the footer too, but we don't hold that against it. mwah 🫶💜🌷

📦 where this page comes from