From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: julia.filipchuk@intel.com, matthew.brost@intel.com,
rodrigo.vivi@intel.com, Zhanjun Dong <zhanjun.dong@intel.com>
Subject: [PATCH v7 0/2] drm/xe/guc: Compress GuC log and CTB dump with zstd
Date: Fri, 31 Jul 2026 11:54:09 -0400 [thread overview]
Message-ID: <20260731155411.496975-1-zhanjun.dong@intel.com> (raw)
GuC snapshot output is currently expensive in both size and latency: large
log buffers are emitted as raw ascii85, and the surrounding dump text
includes a bit of avoidable noise. This series makes xe snapshot dumps more
compact and easier to handle by compressing the large binary payloads,
tightening the textual output.
Select ZSTD_COMPRESS in DRM_XE so the xe module pulls in the zstd
compressor when built.
Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
---
Cc: Julia Filipchuk <julia.filipchuk@intel.com>
History:
v7: Add *why* to the commit message (Rodrigo)
v6: Remove intermediate build files(Julia)
Remvoe unnecessary comment(Julia)
v5: Update cover letter messages to remove shrink log size.
Fix kernel-doc warning.
v4: Remove ZSTD_DECOMPRESS dependency.
v3: Add Kconfig option to control compression of GuC log and CTB dumps,
allowing users to choose between reduced dump sizes or lower memory
usage.
Remove "reduce GuC log size from 8MB to 2MB" patch, to be added later
if needed.
Replace pr_err with xe_gt_err and add more error print.
v2: Fix Kunit test error by selecting ZSTD_DECOMPRESS in DRM_XE config,
required by zstd_is_error/zstd_get_error_name.
Zhanjun Dong (2):
drm/xe: Remove extra newlines from LRC snapshot dump
drm/xe/guc: Compress GuC log and CTB dump with zstd
drivers/gpu/drm/xe/Kconfig | 15 +++
drivers/gpu/drm/xe/xe_devcoredump.c | 4 +-
drivers/gpu/drm/xe/xe_guc_ct.c | 19 ++--
drivers/gpu/drm/xe/xe_guc_ct.h | 4 +-
drivers/gpu/drm/xe/xe_guc_log.c | 161 +++++++++++++++++++++++++---
drivers/gpu/drm/xe/xe_guc_log.h | 9 +-
drivers/gpu/drm/xe/xe_lrc.c | 4 +-
7 files changed, 185 insertions(+), 31 deletions(-)
--
2.34.1
next reply other threads:[~2026-07-31 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 15:54 Zhanjun Dong [this message]
2026-07-31 15:54 ` [PATCH v7 1/2] drm/xe: Remove extra newlines from LRC snapshot dump Zhanjun Dong
2026-07-31 15:54 ` [PATCH v7 2/2] drm/xe/guc: Compress GuC log and CTB dump with zstd Zhanjun Dong
2026-07-31 16:00 ` ✗ CI.checkpatch: warning for drm/xe/guc: Compress GuC log and CTB dump with zstd (rev3) Patchwork
2026-07-31 16:01 ` ✓ CI.KUnit: success " Patchwork
2026-07-31 16:45 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-31 17:39 ` ✗ Xe.CI.FULL: failure " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260731155411.496975-1-zhanjun.dong@intel.com \
--to=zhanjun.dong@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=julia.filipchuk@intel.com \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox