Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Zhanjun Dong <zhanjun.dong@intel.com>
Subject: [PATCH v2 3/3] drm/xe/guc: Reduce GuC log size from 8MB to 2MB
Date: Mon, 11 May 2026 15:49:24 -0400	[thread overview]
Message-ID: <20260511194924.2016315-4-zhanjun.dong@intel.com> (raw)
In-Reply-To: <20260511194924.2016315-1-zhanjun.dong@intel.com>

Reduce the default log buffer size to improve system responsiveness and
readability. The previous 8MB threshold caused significant delays during
log output and imposed a heavy load when printing to dmesg.

By reducing the size to 2MB, we maintain a sufficient history while
ensuring faster flushing. With a typical 4:1 compression ratio, this 2MB
buffer will result in approximately 512KB of compressed data, providing an
efficient balance between log depth and system performance.

Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
---
 drivers/gpu/drm/xe/xe_guc_log.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/xe/xe_guc_log.h b/drivers/gpu/drm/xe/xe_guc_log.h
index d231def50692..44e81a54681f 100644
--- a/drivers/gpu/drm/xe/xe_guc_log.h
+++ b/drivers/gpu/drm/xe/xe_guc_log.h
@@ -17,7 +17,7 @@ struct xe_device;
 #define XE_GUC_LOG_CRASH_DUMP_BUFFER_SIZE	SZ_1M
 #define XE_GUC_LOG_STATE_CAPTURE_BUFFER_SIZE	SZ_2M
 #elif IS_ENABLED(CONFIG_DRM_XE_DEBUG)
-#define XE_GUC_LOG_EVENT_DATA_BUFFER_SIZE	SZ_8M
+#define XE_GUC_LOG_EVENT_DATA_BUFFER_SIZE	SZ_2M
 #define XE_GUC_LOG_CRASH_DUMP_BUFFER_SIZE	SZ_1M
 #define XE_GUC_LOG_STATE_CAPTURE_BUFFER_SIZE	SZ_1M
 #else
-- 
2.34.1


  parent reply	other threads:[~2026-05-11 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 19:49 [PATCH v2 0/3] drm/xe: shrink and compress GuC snapshot dumps Zhanjun Dong
2026-05-11 19:49 ` [PATCH v2 1/3] drm/xe/guc: Compress GuC log and CTB dump with zstd Zhanjun Dong
2026-05-11 19:49 ` [PATCH v2 2/3] drm/xe: Remove extra newlines from LRC snapshot dump Zhanjun Dong
2026-05-11 19:49 ` Zhanjun Dong [this message]
2026-05-12  7:41 ` ✗ CI.checkpatch: warning for drm/xe: shrink and compress GuC snapshot dumps (rev2) Patchwork
2026-05-12  7:42 ` ✓ CI.KUnit: success " Patchwork
2026-05-12  7:58 ` ✗ CI.checksparse: warning " Patchwork
2026-05-12  9:11 ` ✓ Xe.CI.BAT: success " Patchwork
2026-05-12 17:09 ` ✗ 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=20260511194924.2016315-4-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