Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "Summers, Stuart" <stuart.summers@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "dev@lankhorst.se" <dev@lankhorst.se>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/9] drm/xe: Remove double new line in devcoredump
Date: Mon, 22 Jan 2024 18:40:14 +0000	[thread overview]
Message-ID: <1fa902956e2dcd9092934f7587fd1f4fa3e5bd81.camel@intel.com> (raw)
In-Reply-To: <f787dab50690396e0cf1159da66321a85069009c.camel@intel.com>

On Mon, 2024-01-22 at 18:28 +0000, Summers, Stuart wrote:
> On Mon, 2024-01-22 at 09:04 -0800, José Roberto de Souza wrote:
> > Right now devcoredump has a new line between '**** GuC CT ****' and
> > 'H2G CTB (all sizes in DW):' while other sections don't have.
> > 
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Maarten Lankhorst <dev@lankhorst.se>
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_guc_ct.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c
> > b/drivers/gpu/drm/xe/xe_guc_ct.c
> > index ee5d99456aebc..0c07355690948 100644
> > --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> > +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> > @@ -1366,7 +1366,7 @@ void xe_guc_ct_snapshot_print(struct
> > xe_guc_ct_snapshot *snapshot,
> >                 return;
> >  
> >         if (snapshot->ct_enabled) {
> > -               drm_puts(p, "\nH2G CTB (all sizes in DW):\n");
> > +               drm_puts(p, "H2G CTB (all sizes in DW):\n");
> >                 guc_ctb_snapshot_print(&snapshot->h2g, p);
> >  
> >                 drm_puts(p, "\nG2H CTB (all sizes in DW):\n");
> 
> Why not here too?
> 
> Also just visually IMO it is nice to have the extra spacing here. I
> don't have a strong opinion though.

This sections outputs like below what looks fine to me:

**** GuC CT ****
H2G CTB (all sizes in DW):
	size: 1024
	resv_space: 0
	head: 0
	tail: 424
	space: 599
	broken: 0
	head (memory): 424
	tail (memory): 424
	status (memory): 0x0

G2H CTB (all sizes in DW):
	size: 4096
	resv_space: 1024
	head: 137
	tail: 0
	space: 3071
	broken: 0
	head (memory): 137
	tail (memory): 137
	status (memory): 0x0
	g2h outstanding: 0

GuC ID: 2
	Name: rcs2
	Class: 0
	Logical mask: 0x1
	Width: 1
	Ref: 2
	Timeout: 5000 (ms)
	Timeslice: 1000 (us)
	Preempt timeout: 640000 (us)
	HW Context Desc: 0x00435000
	LRC Head: (memory) 416
	LRC Tail: (internal) 552, (memory) 552
	Start seqno: (memory) -124
	Seqno: (memory) -125
	Schedule State: 0x3
	Flags: 0x8

> 
> Thanks,
> Stuart
> 
> > @@ -1375,7 +1375,7 @@ void xe_guc_ct_snapshot_print(struct
> > xe_guc_ct_snapshot *snapshot,
> >                 drm_printf(p, "\tg2h outstanding: %d\n",
> >                            snapshot->g2h_outstanding);
> >         } else {
> > -               drm_puts(p, "\nCT disabled\n");
> > +               drm_puts(p, "CT disabled\n");
> >         }
> >  }
> >  
> 


  reply	other threads:[~2024-01-22 18:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 17:04 [PATCH 1/9] drm/xe: Remove double new line in devcoredump José Roberto de Souza
2024-01-22 17:04 ` [PATCH 2/9] drm/xe: Change devcoredump functions parameters to xe_sched_job José Roberto de Souza
2024-01-22 18:39   ` Summers, Stuart
2024-01-22 17:04 ` [PATCH 3/9] drm/xe: Add functions to convert regular address to canonical address and back José Roberto de Souza
2024-01-22 18:38   ` Summers, Stuart
2024-01-22 18:43     ` Souza, Jose
2024-01-24 15:16       ` Summers, Stuart
2024-01-24 15:20         ` Souza, Jose
2024-01-29 17:54           ` Summers, Stuart
2024-01-23 17:48   ` Jani Nikula
2024-01-22 17:04 ` [PATCH 4/9] drm/xe: Add batch buffer addresses to devcoredump José Roberto de Souza
2024-01-22 20:13   ` Rodrigo Vivi
2024-01-22 17:04 ` [PATCH 5/9] drm/xe: Nuke xe from xe_devcoredump José Roberto de Souza
2024-01-22 20:11   ` Rodrigo Vivi
2024-01-22 20:26     ` Souza, Jose
2024-01-22 20:40       ` Rodrigo Vivi
2024-01-22 17:04 ` [PATCH 6/9] drm/xe: Stash GMD_ID value in xe_gt José Roberto de Souza
2024-01-22 17:04 ` [PATCH 7/9] drm/xe: Print more device information in devcoredump José Roberto de Souza
2024-01-22 20:18   ` Rodrigo Vivi
2024-01-22 21:12     ` Souza, Jose
2024-01-22 17:04 ` [PATCH 8/9] drm/xe: Print registers spread in 2 u32 as u64 José Roberto de Souza
2024-01-22 20:14   ` Rodrigo Vivi
2024-01-22 17:04 ` [PATCH 9/9] drm/xe: Remove addional spaces in devcoredump HW Engines section José Roberto de Souza
2024-01-22 20:18   ` Rodrigo Vivi
2024-01-22 17:32 ` ✓ CI.Patch_applied: success for series starting with [1/9] drm/xe: Remove double new line in devcoredump Patchwork
2024-01-22 17:32 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-22 17:33 ` ✓ CI.KUnit: success " Patchwork
2024-01-22 17:40 ` ✓ CI.Build: " Patchwork
2024-01-22 17:41 ` ✗ CI.Hooks: failure " Patchwork
2024-01-22 17:42 ` ✓ CI.checksparse: success " Patchwork
2024-01-22 18:05 ` ✓ CI.BAT: " Patchwork
2024-01-22 18:28 ` [PATCH 1/9] " Summers, Stuart
2024-01-22 18:40   ` Souza, Jose [this message]
2024-01-22 20:20     ` Rodrigo Vivi
2024-01-24 15:17       ` Summers, Stuart

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=1fa902956e2dcd9092934f7587fd1f4fa3e5bd81.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=dev@lankhorst.se \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=stuart.summers@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