From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2 1/2] drm/xe/guc: Add LFD format output for guc log
Date: Mon, 31 Mar 2025 19:47:59 -0400 [thread overview]
Message-ID: <b893f6a8-6e74-4a92-bdbb-8dfcbcbdf8c3@intel.com> (raw)
In-Reply-To: <Z+YaCmivtd1Wa9wU@lstrano-desk.jf.intel.com>
On 2025-03-27 11:39 p.m., Matthew Brost wrote:
> On Thu, Mar 27, 2025 at 04:40:27PM -0700, Zhanjun Dong wrote:
>> Add new debugfs entry "guc_log_lfd", which supports output guc log
>> in LFD(Log Format Descriptors) format.
>>
>
> Not a full review - but couple of drive by comments.
>
> I suggest trying to split this patch into a series of smaller ones if
> possible. 756 loc is lot for a single patch. Off the top of my head...
>
> - ABI patches
> - New GuC patch
> - New debugfs entry patch
>
Thanks for review, I will make another rev which split into more smaller
ones.
Regards,
Zhanjun
>> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
>> ---
>> drivers/gpu/drm/xe/abi/guc_log_abi.h | 112 +++++++
>> drivers/gpu/drm/xe/abi/guc_log_lfd_abi.h | 261 ++++++++++++++++
>> drivers/gpu/drm/xe/xe_guc_debugfs.c | 14 +
>> drivers/gpu/drm/xe/xe_guc_log.c | 368 +++++++++++++++++++++++
>> drivers/gpu/drm/xe/xe_guc_log.h | 1 +
>> 5 files changed, 756 insertions(+)
>> create mode 100644 drivers/gpu/drm/xe/abi/guc_log_lfd_abi.h
next prev parent reply other threads:[~2025-03-31 23:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 23:40 [PATCH v2 0/2] drm/xe/guc: Add LFD format output for guc log Zhanjun Dong
2025-03-27 23:40 ` [PATCH v2 1/2] " Zhanjun Dong
2025-03-28 3:39 ` Matthew Brost
2025-03-31 23:47 ` Dong, Zhanjun [this message]
2025-04-03 15:20 ` Dong, Zhanjun
2025-04-11 14:38 ` Michal Wajdeczko
2025-04-11 20:21 ` Dong, Zhanjun
2025-03-27 23:40 ` [PATCH v2 2/2] drm/xe/guc: Only add GuC crash dump if available Zhanjun Dong
2025-04-03 21:46 ` John Harrison
2025-04-08 14:51 ` Dong, Zhanjun
2025-03-27 23:45 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add LFD format output for guc log (rev2) Patchwork
2025-03-27 23:45 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-27 23:46 ` ✓ CI.KUnit: success " Patchwork
2025-03-28 0:03 ` ✓ CI.Build: " Patchwork
2025-03-28 0:05 ` ✓ CI.Hooks: " Patchwork
2025-03-28 0:07 ` ✓ CI.checksparse: " Patchwork
2025-03-28 0:28 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-28 13:26 ` ✗ 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=b893f6a8-6e74-4a92-bdbb-8dfcbcbdf8c3@intel.com \
--to=zhanjun.dong@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
/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