From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH v3 0/2] Imrpove GuC debug log/status output
Date: Wed, 8 May 2024 15:49:25 -0700 [thread overview]
Message-ID: <20240508224927.11341-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Improve the robustness and decodeability of GuC log output, especially
when dumped via dmesg. Also remove a spurious line feed that messes up
the GuC status dump when sent to dmesg.
v2: Remote pm calls (Matthew Brost)
v3: Add more info and fix spurious line feed.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (2):
drm/xe/guc: Remove spurious line feed in debug print
drm/xe/guc: Improve robustness of GuC log dumping to dmesg
drivers/gpu/drm/xe/regs/xe_guc_regs.h | 1 +
drivers/gpu/drm/xe/xe_guc_ct.c | 2 +-
drivers/gpu/drm/xe/xe_guc_log.c | 85 ++++++++++++++++++++++-----
3 files changed, 72 insertions(+), 16 deletions(-)
--
2.43.2
next reply other threads:[~2024-05-08 22:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 22:49 John.C.Harrison [this message]
2024-05-08 22:49 ` [PATCH v3 1/2] drm/xe/guc: Remove spurious line feed in debug print John.C.Harrison
2024-05-09 10:18 ` Michal Wajdeczko
2024-05-08 22:49 ` [PATCH v3 2/2] drm/xe/guc: Improve robustness of GuC log dumping to dmesg John.C.Harrison
2024-05-13 15:21 ` Dong, Zhanjun
2024-05-13 17:13 ` John Harrison
2024-05-14 17:32 ` Dong, Zhanjun
2024-05-14 18:18 ` John Harrison
2024-05-14 16:01 ` Michal Wajdeczko
2024-05-14 18:31 ` John Harrison
2024-05-14 21:05 ` Michal Wajdeczko
2024-05-16 0:00 ` John Harrison
2024-05-08 22:54 ` ✓ CI.Patch_applied: success for Imrpove GuC debug log/status output Patchwork
2024-05-08 22:55 ` ✓ CI.checkpatch: " Patchwork
2024-05-08 22:56 ` ✓ CI.KUnit: " Patchwork
2024-05-08 23:07 ` ✓ CI.Build: " Patchwork
2024-05-08 23:10 ` ✓ CI.Hooks: " Patchwork
2024-05-08 23:11 ` ✓ CI.checksparse: " Patchwork
2024-05-08 23:47 ` ✓ CI.BAT: " Patchwork
2024-05-09 12:21 ` ✓ 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=20240508224927.11341-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.