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: michal.wajdeczko@intel.com, Zhanjun Dong <zhanjun.dong@intel.com>
Subject: [PATCH v4 2/2]  drm/xe/guc: Update GuC log buffer type value
Date: Thu,  2 Oct 2025 11:03:02 -0400	[thread overview]
Message-ID: <20251002150302.99524-3-zhanjun.dong@intel.com> (raw)
In-Reply-To: <20251002150302.99524-1-zhanjun.dong@intel.com>

Update GuC log buffer type value, to align with the GuC specification.
Rename GUC_LOG_BUFFER_DEBUG to GUC_LOG_BUFFER_EVENT_LOG.

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;
 	}
 
-- 
2.34.1


  parent reply	other threads:[~2025-10-02 15:03 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 ` Zhanjun Dong [this message]
2025-10-04 16:42   ` [PATCH v4 2/2] drm/xe/guc: Update GuC log buffer type value Michal Wajdeczko
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=20251002150302.99524-3-zhanjun.dong@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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