All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/guc: Increase GuC crash dump buffer size
Date: Thu, 28 Aug 2025 18:19:26 +0000	[thread overview]
Message-ID: <39b6759c8ada538ba44e375c7cb4e38ef824fa79.camel@intel.com> (raw)
In-Reply-To: <20250827212110.1024961-1-zhanjun.dong@intel.com>

On Wed, 2025-08-27 at 17:21 -0400, Zhanjun Dong wrote:
> Increase GuC crash dump buffer size to support up to 16K dump size.

But why do we need to do this?

-Stuart

> 
> 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 f1e2b0be90a9..98a47ac42b08 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 DEBUG_BUFFER_SIZE       SZ_8M
>  #define CAPTURE_BUFFER_SIZE     SZ_2M
>  #else
> -#define CRASH_BUFFER_SIZE      SZ_8K
> +#define CRASH_BUFFER_SIZE      SZ_16K
>  #define DEBUG_BUFFER_SIZE      SZ_64K
>  #define CAPTURE_BUFFER_SIZE    SZ_1M
>  #endif


  parent reply	other threads:[~2025-08-28 18:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27 21:21 [PATCH] drm/xe/guc: Increase GuC crash dump buffer size Zhanjun Dong
2025-08-27 23:34 ` ✓ CI.KUnit: success for " Patchwork
2025-08-28  0:13 ` ✓ Xe.CI.BAT: " Patchwork
2025-08-28  1:20 ` ✗ Xe.CI.Full: failure " Patchwork
2025-08-28 18:19 ` Summers, Stuart [this message]
2025-08-28 21:33   ` [PATCH] " John Harrison
2025-08-28 21:34     ` Summers, Stuart

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=39b6759c8ada538ba44e375c7cb4e38ef824fa79.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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.