From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Zhanjun Dong <zhanjun.dong@intel.com>
Subject: [PATCH 0/3] drm/xe: shrink and compress GuC snapshot dumps
Date: Thu, 7 May 2026 14:06:15 -0400 [thread overview]
Message-ID: <20260507180618.1420986-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, and trimming the default GuC log size.
Select ZSTD_COMPRESS in DRM_XE so the xe module pulls in the zstd
compressor when built.
Reduces the default GuC log buffer from 8MB to 2MB, which still preserves
useful history while cutting dump latency and dmesg load; with typical
compression, the emitted payload drops further.
Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
Zhanjun Dong (3):
drm/xe/guc: Compress GuC log and CTB dump with zstd
drm/xe: Remove extra newlines from LRC snapshot dump
drm/xe/guc: Reduce GuC log size from 8MB to 2MB
drivers/gpu/drm/xe/Kconfig | 1 +
drivers/gpu/drm/xe/xe_guc_ct.c | 9 ++-
drivers/gpu/drm/xe/xe_guc_log.c | 110 ++++++++++++++++++++++++++++----
drivers/gpu/drm/xe/xe_guc_log.h | 5 +-
drivers/gpu/drm/xe/xe_lrc.c | 4 +-
5 files changed, 108 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2026-05-07 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 18:06 Zhanjun Dong [this message]
2026-05-07 18:06 ` [PATCH 1/3] drm/xe/guc: Compress GuC log and CTB dump with zstd Zhanjun Dong
2026-05-07 18:06 ` [PATCH 2/3] drm/xe: Remove extra newlines from LRC snapshot dump Zhanjun Dong
2026-05-07 18:06 ` [PATCH 3/3] drm/xe/guc: Reduce GuC log size from 8MB to 2MB Zhanjun Dong
2026-05-07 18:43 ` ✗ CI.checkpatch: warning for drm/xe: shrink and compress GuC snapshot dumps Patchwork
2026-05-07 18:43 ` ✗ CI.KUnit: 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=20260507180618.1420986-1-zhanjun.dong@intel.com \
--to=zhanjun.dong@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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