From: "José Roberto de Souza" <jose.souza@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH v2 0/2] Enable GuC log dump and minor fixes in devcoredump
Date: Thu, 23 Jan 2025 12:22:02 -0800 [thread overview]
Message-ID: <20250123202307.95103-1-jose.souza@intel.com> (raw)
This patches enables dump GuC log dump again and don't require any
change in Mesa parser.
I will follow up with some changes in Mesa parser to not output
the GuC log binaries but bo and hw context parser are still functional
without those changes.
v2:
- added suffix description comment
- renamed GUC binary to LOG
José Roberto de Souza (1):
drm/xe: Make GUC binaries dump consistent with other binaries in
devcoredump
Lucas De Marchi (1):
drm/xe: Fix and re-enable xe_print_blob_ascii85()
drivers/gpu/drm/xe/xe_devcoredump.c | 33 +++++++++++------------------
drivers/gpu/drm/xe/xe_devcoredump.h | 2 +-
drivers/gpu/drm/xe/xe_guc_ct.c | 7 ++++--
drivers/gpu/drm/xe/xe_guc_log.c | 5 ++++-
4 files changed, 22 insertions(+), 25 deletions(-)
--
2.48.1
next reply other threads:[~2025-01-23 20:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 20:22 José Roberto de Souza [this message]
2025-01-23 20:22 ` [PATCH v2 1/2] drm/xe: Fix and re-enable xe_print_blob_ascii85() José Roberto de Souza
2025-01-23 21:14 ` John Harrison
2025-01-23 21:16 ` John Harrison
2025-01-27 20:26 ` Lucas De Marchi
2025-01-23 20:22 ` [PATCH v2 2/2] drm/xe: Make GUC binaries dump consistent with other binaries in devcoredump José Roberto de Souza
2025-01-23 20:29 ` ✓ CI.Patch_applied: success for Enable GuC log dump and minor fixes in devcoredump (rev2) Patchwork
2025-01-23 20:29 ` ✓ CI.checkpatch: " Patchwork
2025-01-23 20:31 ` ✓ CI.KUnit: " Patchwork
2025-01-23 20:47 ` ✓ CI.Build: " Patchwork
2025-01-23 20:49 ` ✗ CI.Hooks: failure " Patchwork
2025-01-28 15:45 ` Lucas De Marchi
2025-01-23 20:51 ` ✓ CI.checksparse: success " Patchwork
2025-01-23 21:36 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-24 7:44 ` ✗ 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=20250123202307.95103-1-jose.souza@intel.com \
--to=jose.souza@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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