xe_devcoredump(9)
π xe_devcoredump(9) π
okay so this is a page from the Kernel API Manual and it's literally about the moment everything goes π β welcome to xe_devcoredump, bestie π«Ά
β¨ NAME β¨
xe_devcoredump β take the required snapshots and initialize coredump device. no cap, that's the whole vibe π
πΈ SYNOPSIS πΈ
void xe_devcoredump (struct xe_exec_queue *q , struct xe_sched_job *job
, const char *fmt , ... );
π¦ ARGUMENTS π¦
qβ the faultyxe_exec_queue, like, the exact spot where the issue was detected πjobβ the faultyxe_sched_job, again, where the issue was detected π₯fmtβ a printf format + args, and you use it to describe the reason for the core dump. spill the tea fr fr π...β variable arguments π«
π DESCRIPTION π
so here's the deal: this function should be called at the crash time, within the serialized gt_reset. that's not optional energy, that's the requirement π¨
and like β it gets skipped if we still have the core dump device available with the information of the 'first' snapshot. so the first one wins, periodt π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/xe/xe_devcoredump.c - Xe device coredump(9)
xe_devcoredump_read(9)xe_print_blob_ascii85(9)
and that's the whole page bestie, go forth and snapshot β¨
shoutout to the source/version it lives under, ./drivers/gpu/drm/xe, dated October 2026 β that's the cute little sign-off, mwah ππ§
π¦ 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