xe_guc_ct_snapshot_capture(9)
π xe_guc_ct_snapshot_capture(9) π
okay bestie, this is the Kernel API Manual page for xe_guc_ct_snapshot_capture β long title, useful function, and we're getting into it β¨
β¨ NAME β¨
xe_guc_ct_snapshot_capture β take a quick snapshot of the CT state. literally that's her job π
πΈ SYNOPSIS πΈ
the whole signature, no cap:
struct xe_guc_ct_snapshot * xe_guc_ct_snapshot_capture (struct xe_guc_ct
*ct );
π ARGUMENTS π
ctβ the GuC CT object. hand it over, bestie, that's the vibe.
π DESCRIPTION π
okay so this is the part where she takes a snapshot of the CT state. It can be printed out at a later stage β like during dev_coredump analysis. And yes, it is safe to be called during atomic context. no cap, that matters πβ¨
π RETURN π
You get back a GuC CT snapshot object. It must be freed by the caller using xe_guc_ct_snapshot_free β don't leave it hanging, bestie π«Ά
π¦ SEE ALSO π¦
the kernel file and the whole squad, periodt:
- Kernel file
./drivers/gpu/drm/xe/xe_guc_ct.c GuC CTB Blob(9)xe_guc_ct_queue_proc_time_jiffies(9)xe_guc_ct_init_post_hwconfig(9)xe_guc_ct_restart(9)xe_guc_ct_enable(9)xe_guc_ct_disable(9)xe_guc_ct_flush_and_stop(9)xe_guc_ct_stop(9)xe_guc_ct_runtime_suspend(9)xe_guc_ct_runtime_resume(9)xe_guc_ct_send(9)xe_guc_ct_send_recv(9)xe_guc_ct_fast_path(9)xe_guc_ct_snapshot_print(9)xe_guc_ct_snapshot_free(9)xe_guc_ct_print(9)
Source/version check: ./drivers/gpu/drm/xe + Kernel API Manual, dated October 2026 β xe_guc_ct_snapshot_capture(9) signing off π«Άπ
π¦ 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