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: Zhanjun Dong <zhanjun.dong@intel.com>,
	Michal Wajdeczko <michal.wajdeczko@intel.com>,
	John Harrison <john.c.harrison@intel.com>
Subject: [PATCH v2 0/2] drm/xe/guc: Add LFD format output for guc log
Date: Thu, 27 Mar 2025 16:40:26 -0700	[thread overview]
Message-ID: <20250327234028.249314-1-zhanjun.dong@intel.com> (raw)

Add new debugfs entry "guc_log_lfd", which supports output guc log
in LFD(Log Format Descriptors) format.
Add flag of GuC crash dump received. LFD only include crash dump
section when this flag is set.

Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: John Harrison <john.c.harrison@intel.com>

Changes in v2:
Split GuC init config abi defines out from LFD abi header file
Split crash dump detect as seperate patch
Add size check for LFD functions
Make abi header comments kernel-doc style

Zhanjun Dong (2):
  drm/xe/guc: Add LFD format output for guc log
  drm/xe/guc: Only add GuC crash dump if available

 drivers/gpu/drm/xe/abi/guc_log_abi.h     | 112 +++++++
 drivers/gpu/drm/xe/abi/guc_log_lfd_abi.h | 261 +++++++++++++++
 drivers/gpu/drm/xe/xe_guc_ct.c           |  13 +-
 drivers/gpu/drm/xe/xe_guc_debugfs.c      |  14 +
 drivers/gpu/drm/xe/xe_guc_log.c          | 398 +++++++++++++++++++++++
 drivers/gpu/drm/xe/xe_guc_log.h          |   1 +
 drivers/gpu/drm/xe/xe_guc_log_types.h    |   2 +
 7 files changed, 796 insertions(+), 5 deletions(-)
 create mode 100644 drivers/gpu/drm/xe/abi/guc_log_lfd_abi.h

-- 
2.34.1


             reply	other threads:[~2025-03-27 23:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 23:40 Zhanjun Dong [this message]
2025-03-27 23:40 ` [PATCH v2 1/2] drm/xe/guc: Add LFD format output for guc log Zhanjun Dong
2025-03-28  3:39   ` Matthew Brost
2025-03-31 23:47     ` Dong, Zhanjun
2025-04-03 15:20     ` Dong, Zhanjun
2025-04-11 14:38       ` Michal Wajdeczko
2025-04-11 20:21         ` Dong, Zhanjun
2025-03-27 23:40 ` [PATCH v2 2/2] drm/xe/guc: Only add GuC crash dump if available Zhanjun Dong
2025-04-03 21:46   ` John Harrison
2025-04-08 14:51     ` Dong, Zhanjun
2025-03-27 23:45 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add LFD format output for guc log (rev2) Patchwork
2025-03-27 23:45 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-27 23:46 ` ✓ CI.KUnit: success " Patchwork
2025-03-28  0:03 ` ✓ CI.Build: " Patchwork
2025-03-28  0:05 ` ✓ CI.Hooks: " Patchwork
2025-03-28  0:07 ` ✓ CI.checksparse: " Patchwork
2025-03-28  0:28 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-28 13:26 ` ✗ Xe.CI.Full: failure " 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=20250327234028.249314-1-zhanjun.dong@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    --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