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 0/2] drm/xe/guc: Cleanup GuC log buffer macros and helpers
Date: Thu, 2 Oct 2025 11:03:00 -0400 [thread overview]
Message-ID: <20251002150302.99524-1-zhanjun.dong@intel.com> (raw)
Cleanup GuC log buffer macros and helpers, add Xe style macro prefix.
Update buffer type values to align with the GuC specification
---
Cc: michal.wajdeczko@intel.com
---
Change list:
v4: Replace helper functions with macros
Rename log type xxx_DEBUG to xxx_EVENT_LOG
v3: Update comments
v2: Use SZ_4K, instead of PAGE_SIZE
Expand for loop with switch and fallthrough
Zhanjun Dong (2):
drm/xe/guc: Add prefix to guc log buffer macros
drm/xe/guc: Update GuC log buffer type value
drivers/gpu/drm/xe/abi/guc_log_abi.h | 2 +-
drivers/gpu/drm/xe/xe_guc.c | 22 ++++-----
drivers/gpu/drm/xe/xe_guc_capture.c | 6 +--
drivers/gpu/drm/xe/xe_guc_log.c | 71 +++++++---------------------
drivers/gpu/drm/xe/xe_guc_log.h | 14 +++---
5 files changed, 37 insertions(+), 78 deletions(-)
--
2.34.1
next 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 Zhanjun Dong [this message]
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
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-1-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