xe_guc_exec_...ture_delayed(9)

📦 version 7.3.1, in nixpkgs unstable

💜 xe_guc_exec_...ture_delayed(9) — like, the whole entire glow-up 💜

okay so bestie, welcome to the Kernel API Manual (yes, the Kernel API Manual, we're in the big leagues now 🎀). This page is all about xe_guc_exec_queue_snapshot_capture_delayed, which — and I cannot stress this enough — is a long name. Like, it ate and left no crumbs, but it also left no vowels. Anyway. Let's get into it ✨

🌸 NAME 🌸

xe_guc_exec_queue_snapshot_capture_delayed — takes the delayed part of a snapshot of the GuC Engine. That's it, that's the vibe. 🦋

✨ SYNOPSIS ✨

void xe_guc_exec_queue_snapshot_capture_delayed (struct
xe_guc_submit_exec_queue_snapshot *snapshot );

literal copy-paste energy (but like, the good kind), no cap 🫶

🎀 ARGUMENTS 🎀

  • snapshot — the previously captured snapshot of the job. like, it already exists, you're just adding to it, main character energy but make it teamwork 💅

🔥 DESCRIPTION 🔥

so here's the tea ☕: this function captures some data, right? but this data is special — it requires taking some locks. and because it needs locks, it cannot be done in the signaling path. nope. not happening. not there. 🙈

it's giving "delayed for a reason" and honestly? iconic. the signaling path stays fast, this part waits its turn, everybody wins. periodt. 👑

💖 SEE ALSO 💖

okay this section is stacked, bestie — look at all these friends:

a whole friend group, fr fr 🌈💜

aaaand that's the page!! mwah 💋 before you go: this lil masterpiece lives in ./drivers/gpu/drm/xe, and it's dated October 2026 — so yeah, she's from the future, we don't question it ⭐🦋 go forth and capture those delayed snapshots, bestie, you got this 💖✨🎀

📦 where this page comes from