Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
	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: Fri, 11 Apr 2025 16:38:15 +0200	[thread overview]
Message-ID: <55fcfe89-2eb2-48bc-93f9-bb02109097bd@intel.com> (raw)
In-Reply-To: <ce6d3489-ee79-4834-b4be-1c5a590d682d@intel.com>



On 03.04.2025 17:20, Dong, Zhanjun wrote:
> Please see my inline comments below.
> 
> Regards,
> Zhanjun Dong
> 
> 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.
>>

...

>>> +
>>> +/** Log Init Config KLV IDs. */
>>> +enum guc_log_lic_type_t {
>>
>> '_t' suffix isn't used in the Xe style as typically is used for typedefs
>> which are frowned upon in upstream Linux. I'd drop "_t" suffix
>> everywhere.
> 
> I agree _t is not Xe style, while for this case, the ABI header file is
> follows with GuC spec, which is a cross system/project thing. The name
> here is the secondary defines.
> I guess simply follows orginal spec will make things more easy to
> compare and reduce possible mismatches among systems.
> 

I was also requesting to drop the _t suffix, so it's not just Matt voice

also please note that the raw GuC spec is not based on some solid ISO
standard that we should use as a role model, so blindly following what
was written there is not exactly the right choice

and while comparing spec you can easily drop _t suffix (that shouldn't
be there in first place)



  reply	other threads:[~2025-04-11 14:38 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
2025-04-03 15:20     ` Dong, Zhanjun
2025-04-11 14:38       ` Michal Wajdeczko [this message]
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=55fcfe89-2eb2-48bc-93f9-bb02109097bd@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=zhanjun.dong@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