From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
"Brost, Matthew" <matthew.brost@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Filipchuk, Julia" <julia.filipchuk@intel.com>
Subject: Re: [PATCH v8 0/2] drm/xe/guc: Compress GuC log and CTB dump with zstd
Date: Wed, 2 Sep 2026 23:37:53 +0000 [thread overview]
Message-ID: <4c60954550bb53cfcc427b51c09d7746f55b48e6.camel@intel.com> (raw)
In-Reply-To: <20260902224417.879960-4-alan.previn.teres.alexis@intel.com>
Please ignore this series. I will resend without in-reply-to which has caused issues on patchworks pickup.
Apologies for the trouble.
...alan
On Wed, 2026-09-02 at 15:44 -0700, Alan Previn wrote:
> 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>
>
>
[snip]
next prev parent reply other threads:[~2026-09-02 23:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 15:54 [PATCH v7 0/2] drm/xe/guc: Compress GuC log and CTB dump with zstd Zhanjun Dong
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-08-05 1:07 ` Rodrigo Vivi
2026-08-05 13:47 ` Souza, Jose
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
2026-09-02 22:44 ` [PATCH v8 0/2] drm/xe/guc: Compress GuC log and CTB dump with zstd Alan Previn
2026-09-02 22:44 ` [PATCH v8 1/2] drm/xe: Remove extra newlines from LRC snapshot dump Alan Previn
2026-09-02 22:44 ` [PATCH v8 2/2] drm/xe/guc: Compress GuC log and CTB dump with zstd Alan Previn
2026-09-02 22:59 ` sashiko-bot
2026-09-02 23:37 ` Teres Alexis, Alan Previn [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-02 23:40 [PATCH v8 0/2] " Alan Previn
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=4c60954550bb53cfcc427b51c09d7746f55b48e6.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=julia.filipchuk@intel.com \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=zhanjun.dong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.