From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH v4 0/2] Imrpove GuC debug log/status output
Date: Tue, 14 May 2024 12:08:17 -0700 [thread overview]
Message-ID: <20240514190819.1970533-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: Remove pm calls (Matthew Brost).
v3: Add more info and fix spurious line feed.
v4: Add kernel doc and macro clean up (Michal W).
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 | 101 ++++++++++++++++++++++----
3 files changed, 88 insertions(+), 16 deletions(-)
--
2.43.2
next reply other threads:[~2024-05-14 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 19:08 John.C.Harrison [this message]
2024-05-14 19:08 ` [PATCH v4 1/2] drm/xe/guc: Remove spurious line feed in debug print John.C.Harrison
2024-05-14 19:08 ` [PATCH v4 2/2] drm/xe/guc: Improve robustness of GuC log dumping to dmesg John.C.Harrison
2024-05-14 19:49 ` ✓ CI.Patch_applied: success for Imrpove GuC debug log/status output (rev2) Patchwork
2024-05-14 19:50 ` ✓ CI.checkpatch: " Patchwork
2024-05-14 19:50 ` ✓ CI.KUnit: " Patchwork
2024-05-14 20:02 ` ✓ CI.Build: " Patchwork
2024-05-14 20:05 ` ✓ CI.Hooks: " Patchwork
2024-05-14 20:06 ` ✓ CI.checksparse: " Patchwork
2024-05-14 20:29 ` ✗ CI.BAT: failure " Patchwork
2024-05-14 22:09 ` ✗ 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=20240514190819.1970533-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