Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH 0/3] Re-instate GuC logs in debugfs & devcoredump
Date: Wed, 22 Jan 2025 13:45:58 -0800	[thread overview]
Message-ID: <20250122214601.3560156-1-John.C.Harrison@Intel.com> (raw)

From: John Harrison <John.C.Harrison@Intel.com>

Remove the appareance of line wrapping in the GuC log output to
prevent confusing a mesa tool and re-instate GuC logs in both
devcoredump and debugfs.

Signed-off-by: John Harrison <John.C.Harrison@Intel.com>


John Harrison (3):
  drm/xe/guc: Explicitly name each chunk of GuC log data in a dump
  drm/xe/devcoredump: Temporarily disable the line wrapping of ASCII85
    output
  Partially revert "drm/xe: Revert some changes that break a mesa debug
    tool"

 drivers/gpu/drm/xe/xe_devcoredump.c | 12 ++----------
 drivers/gpu/drm/xe/xe_guc_log.c     |  4 +++-
 2 files changed, 5 insertions(+), 11 deletions(-)

-- 
2.47.0


             reply	other threads:[~2025-01-22 21:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 21:45 John.C.Harrison [this message]
2025-01-22 21:45 ` [PATCH 1/3] drm/xe/guc: Explicitly name each chunk of GuC log data in a dump John.C.Harrison
2025-01-22 21:46 ` [PATCH 2/3] drm/xe/devcoredump: Temporarily disable the line wrapping of ASCII85 output John.C.Harrison
2025-01-22 21:46 ` [PATCH 3/3] Partially revert "drm/xe: Revert some changes that break a mesa debug tool" John.C.Harrison
2025-01-22 21:54 ` ✓ CI.Patch_applied: success for Re-instate GuC logs in debugfs & devcoredump Patchwork
2025-01-22 21:54 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-22 21:55 ` ✓ CI.KUnit: success " Patchwork
2025-01-22 22:02 ` ✗ CI.Build: 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=20250122214601.3560156-1-John.C.Harrison@Intel.com \
    --to=john.c.harrison@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