xe_guc_log_snapshot_capture(9)
π 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 π§
- Kernel file:
./drivers/gpu/drm/xe/xe_guc_log.cπ xe_guc_log_snapshot_free(9)π«Άxe_guc_log_snapshot_print(9)π¨οΈxe_guc_log_print_dmesg(9)πxe_guc_log_print(9)β¨xe_guc_log_print_lfd(9)πxe_guc_check_log_buf_overflow(9)π₯
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms