xe_guc_log_snapshot_capture(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– xe_guc_log_snapshot_capture β€” Kernel API Manual (9) πŸ’–

okay so bestie, welcome to the xe_guc_log_snapshot_capture page πŸ’… this is a kernel API manual, and we're about to make a whole copy of the GuC log so you can dump it later. yes, it's giving "screenshot before the crash" energy and honestly? obsessed 🫢


✨ NAME ✨

xe_guc_log_snapshot_capture β€” create a new snapshot copy of the GuC log for later dumping 🌸

like, it snatches a copy of the log right now and holds onto it, so you can print it out at your own pace later. main character energy fr fr πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

struct xe_guc_log_snapshot * xe_guc_log_snapshot_capture (struct xe_guc_log *log , bool atomic );

that's the whole signature, no cap β€” it takes a struct xe_guc_log *log and a bool atomic, and hands you back a struct xe_guc_log_snapshot * ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • log β€” the GuC log structure πŸ’– this is the log you're snapshotting, the whole reason we're here.
  • atomic β€” is the call inside an atomic section of some kind? πŸ€” like, are you in atomic context right now? answer honestly, bestie.

🌈 RETURN 🌈

it returns a pointer to a newly allocated snapshot object πŸŽ€ β€” or null if we're out of memory 😭 (yes, NULL is a real possibility, don't @ me).

⚠️ heads up, gorgeous: the caller is responsible for calling xe_guc_log_snapshot_free when done with the snapshot. it's literally yours to clean up. don't leave it hanging, that's not the vibe πŸ’€

🧚 SEE ALSO 🧚


and that's the page, bestie πŸ’œ that's a wrap from ./drivers/gpu/drm/xe, dated October 2026, xe_guc_log_snapshot_capture(9) β€” go forth, snapshot responsibly, and free your snapshots πŸŒΈπŸŽ€πŸ‘‘

πŸ“¦ where this page comes from