From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
linux-fsdevel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH 0/4] Expose raw access to GuC log over debugfs
Date: Sun, 12 May 2024 17:36:02 +0200 [thread overview]
Message-ID: <20240512153606.1996-1-michal.wajdeczko@intel.com> (raw)
We already provide the content of the GuC log in debugsfs, but it
is in a text format where each log dword is printed as hexadecimal
number, which does not scale well with large GuC log buffers.
Cc: linux-fsdevel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org
Michal Wajdeczko (4):
libfs: add simple_read_from_iomem()
iosys-map: add iosys_map_read_from() helper
drm/xe: Add wrapper for iosys_map_read_from
drm/xe/guc: Expose raw access to GuC log over debugfs
drivers/gpu/drm/xe/xe_guc_debugfs.c | 26 +++++++++++++++
drivers/gpu/drm/xe/xe_map.h | 9 ++++++
fs/libfs.c | 50 +++++++++++++++++++++++++++++
include/linux/fs.h | 3 ++
include/linux/iosys-map.h | 24 ++++++++++++++
5 files changed, 112 insertions(+)
--
2.43.0
next reply other threads:[~2024-05-12 15:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 15:36 Michal Wajdeczko [this message]
2024-05-12 15:36 ` [PATCH 1/4] libfs: add simple_read_from_iomem() Michal Wajdeczko
2024-05-12 15:36 ` [PATCH 2/4] iosys-map: add iosys_map_read_from() helper Michal Wajdeczko
2024-05-12 15:36 ` [PATCH 3/4] drm/xe: Add wrapper for iosys_map_read_from Michal Wajdeczko
2024-05-12 15:36 ` [PATCH 4/4] drm/xe/guc: Expose raw access to GuC log over debugfs Michal Wajdeczko
2024-05-13 16:53 ` John Harrison
2024-05-14 14:58 ` Michal Wajdeczko
2024-05-14 18:13 ` John Harrison
2024-05-14 20:31 ` Matthew Brost
2024-05-14 21:15 ` Michal Wajdeczko
2024-05-14 21:54 ` John Harrison
2024-05-14 22:31 ` Matthew Brost
2024-05-14 20:41 ` Michal Wajdeczko
2024-05-14 22:15 ` John Harrison
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=20240512153606.1996-1-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).