From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Zhanjun Dong <zhanjun.dong@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: <stuart.summers@intel.com>, <john.c.harrison@intel.com>
Subject: Re: [PATCH v2] drm/xe/guc: Update GuC log buffer type value
Date: Wed, 24 Sep 2025 00:20:01 +0200 [thread overview]
Message-ID: <44a754f4-78a3-4cbd-9f1f-55d62f19c957@intel.com> (raw)
In-Reply-To: <20250904151406.736972-1-zhanjun.dong@intel.com>
On 9/4/2025 5:14 PM, Zhanjun Dong wrote:
> Update GuC log buffer type value, to align with the GuC specification.
>
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
> ---
> Change list:
> v2: Use SZ_4K, instead of PAGE_SIZE
> Expand for loop with switch and fallthrough
> ---
> drivers/gpu/drm/xe/abi/guc_log_abi.h | 2 +-
> drivers/gpu/drm/xe/xe_guc_log.c | 20 ++++++++++++--------
> 2 files changed, 13 insertions(+), 9 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..b1819679fa35 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_CRASH_DUMP,
> GUC_LOG_BUFFER_DEBUG,
> + GUC_LOG_BUFFER_CRASH_DUMP,
> 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 c01ccb35dc75..6cbb0378d2ba 100644
> --- a/drivers/gpu/drm/xe/xe_guc_log.c
> +++ b/drivers/gpu/drm/xe/xe_guc_log.c
> @@ -50,7 +50,7 @@ static size_t guc_log_size(void)
> * | Capture state header |
> * +-------------------------------+ 96B
> * | |
> - * +===============================+ PAGE_SIZE (4KB)
> + * +===============================+ 4KB
> * | Crash Dump logs |
> * +===============================+ + CRASH_SIZE
> * | Debug logs |
> @@ -58,7 +58,7 @@ static size_t guc_log_size(void)
> * | Capture logs |
> * +===============================+ + CAPTURE_SIZE
> */
> - return PAGE_SIZE + CRASH_BUFFER_SIZE + DEBUG_BUFFER_SIZE +
> + return SZ_4K + CRASH_BUFFER_SIZE + DEBUG_BUFFER_SIZE +
> CAPTURE_BUFFER_SIZE;
nit: can you do the math in the same order as on diagram?
return 4K + DEBUG + CRASH + CAPTURE
and btw, since in this function you are using hardcoded values
> }
>
> @@ -327,13 +327,17 @@ u32 xe_guc_get_log_buffer_size(struct xe_guc_log *log, enum guc_log_buffer_type
> */
> u32 xe_guc_get_log_buffer_offset(struct xe_guc_log *log, enum guc_log_buffer_type type)
> {
> - enum guc_log_buffer_type i;
> - u32 offset = PAGE_SIZE;/* for the log_buffer_states */
> + u32 offset = SZ_4K; /* 1st section size */
>
> - for (i = GUC_LOG_BUFFER_CRASH_DUMP; i < GUC_LOG_BUFFER_TYPE_MAX; ++i) {
> - if (i == type)
> - break;
> - offset += xe_guc_get_log_buffer_size(log, i);
> + switch (type) {
> + case GUC_LOG_BUFFER_CAPTURE:
> + offset += xe_guc_get_log_buffer_size(log, GUC_LOG_BUFFER_CRASH_DUMP);
do we need to use fancy helpers to finally get the same hardcoded value?
here it is just CRASH_BUFFER_SIZE
> + fallthrough;
> + case GUC_LOG_BUFFER_CRASH_DUMP:
> + offset += xe_guc_get_log_buffer_size(log, GUC_LOG_BUFFER_DEBUG);
and here DEBUG_BUFFER_SIZE
> + fallthrough;
> + case GUC_LOG_BUFFER_DEBUG:
> + break;
> }
>
> return offset;
then since XXX_BUFFER_SIZE macros are already in .h maybe we get kill those helpers?
and btw, those BUFFER_SIZE macros in .h should have likely have XE_GUC_LOG prefix
(since those are Xe driver specific) - something for next (or prerequisite patch)
next prev parent reply other threads:[~2025-09-23 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 15:14 [PATCH v2] drm/xe/guc: Update GuC log buffer type value Zhanjun Dong
2025-09-04 16:29 ` ✓ CI.KUnit: success for drm/xe/guc: Update GuC log buffer type value (rev2) Patchwork
2025-09-04 17:02 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-05 7:50 ` ✓ Xe.CI.Full: " Patchwork
2025-09-23 22:20 ` Michal Wajdeczko [this message]
2025-09-25 15:20 ` [PATCH v2] drm/xe/guc: Update GuC log buffer type value Dong, Zhanjun
2025-09-25 17:16 ` Michal Wajdeczko
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=44a754f4-78a3-4cbd-9f1f-55d62f19c957@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=stuart.summers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox