Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Zhanjun Dong <zhanjun.dong@intel.com>,
	<intel-xe@lists.freedesktop.org>,
	Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v4 2/2] drm/xe/guc: Update GuC log buffer type value
Date: Sat, 4 Oct 2025 18:42:15 +0200	[thread overview]
Message-ID: <df58cadf-80d2-4c6b-92d9-beeb8630fc5a@intel.com> (raw)
In-Reply-To: <20251002150302.99524-3-zhanjun.dong@intel.com>



On 10/2/2025 5:03 PM, Zhanjun Dong wrote:
> Update GuC log buffer type value, to align with the GuC specification.
> Rename GUC_LOG_BUFFER_DEBUG to GUC_LOG_BUFFER_EVENT_LOG.

hmm, my copy of GuC specification has:

	GENERAL = 0	/* Log event data */
	CRASH = 1	/* Raw crash data */ 
	ERROR_STATE_CAPTURE = 2	/* Error State Capture data */

so if the goal is to align (more) with the spec, maybe it should be (to keep them reasonable short):

	GENERAL_LOG
	CRASH_DUMP
	ERROR_CAPTURE

+ @Daniele

and btw, IMO this patch should be before the other one that cleanups macros

> 
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
> ---
>  drivers/gpu/drm/xe/abi/guc_log_abi.h | 2 +-
>  drivers/gpu/drm/xe/xe_guc_log.c      | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/abi/guc_log_abi.h b/drivers/gpu/drm/xe/abi/guc_log_abi.h
> index 554630b7ccd9..1a487164b980 100644
> --- a/drivers/gpu/drm/xe/abi/guc_log_abi.h
> +++ b/drivers/gpu/drm/xe/abi/guc_log_abi.h
> @@ -10,8 +10,8 @@
>  
>  /* GuC logging buffer types */
>  enum guc_log_buffer_type {
> +	GUC_LOG_BUFFER_EVENT_LOG,
>  	GUC_LOG_BUFFER_CRASH_DUMP,
> -	GUC_LOG_BUFFER_DEBUG,
>  	GUC_LOG_BUFFER_CAPTURE,
>  };

>  
> diff --git a/drivers/gpu/drm/xe/xe_guc_log.c b/drivers/gpu/drm/xe/xe_guc_log.c
> index fa1d490dca0d..900b39fc734f 100644
> --- a/drivers/gpu/drm/xe/xe_guc_log.c
> +++ b/drivers/gpu/drm/xe/xe_guc_log.c
> @@ -293,7 +293,7 @@ u32 xe_guc_get_log_buffer_offset(struct xe_guc_log *log, enum guc_log_buffer_typ
>  	case GUC_LOG_BUFFER_CRASH_DUMP:
>  		offset += XE_GUC_LOG_EVENT_LOG_BUFFER_SIZE;
>  		fallthrough;
> -	case GUC_LOG_BUFFER_DEBUG:
> +	case GUC_LOG_BUFFER_EVENT_LOG:
>  		break;
>  	}
>  


  reply	other threads:[~2025-10-04 16:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 15:03 [PATCH v4 0/2] drm/xe/guc: Cleanup GuC log buffer macros and helpers Zhanjun Dong
2025-10-02 15:03 ` [PATCH v4 1/2] drm/xe/guc: Add prefix to guc log buffer macros Zhanjun Dong
2025-10-02 16:00   ` Lucas De Marchi
2025-10-02 17:24     ` Lucas De Marchi
2025-10-07 16:44     ` Dong, Zhanjun
2025-10-07 17:08       ` Lucas De Marchi
2025-10-09 17:54         ` Dong, Zhanjun
2025-10-09 19:12           ` Michal Wajdeczko
2025-10-04 17:13   ` Michal Wajdeczko
2025-10-02 15:03 ` [PATCH v4 2/2] drm/xe/guc: Update GuC log buffer type value Zhanjun Dong
2025-10-04 16:42   ` Michal Wajdeczko [this message]
2025-10-09 14:38     ` Dong, Zhanjun
2025-10-02 15:35 ` ✓ CI.KUnit: success for drm/xe/guc: Cleanup GuC log buffer macros and helpers Patchwork
2025-10-02 16:18 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-02 18:48 ` ✓ Xe.CI.Full: " 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=df58cadf-80d2-4c6b-92d9-beeb8630fc5a@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=daniele.ceraolospurio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox