All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: John Harrison <john.c.harrison@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 5/7] drm/i915/guc: Add extra debug on CT deadlock
Date: Fri, 10 Dec 2021 19:24:57 -0800	[thread overview]
Message-ID: <20211211032457.GA8882@jons-linux-dev-box> (raw)
In-Reply-To: <f9938176-8f9c-cdd5-93ad-15046bc95703@intel.com>

On Fri, Dec 10, 2021 at 05:45:05PM -0800, John Harrison wrote:
> On 12/10/2021 17:43, John Harrison wrote:
> > On 12/10/2021 16:56, Matthew Brost wrote:
> > > Print CT state (H2G + G2H head / tail pointers, credits) on CT
> > > deadlock.
> > > 
> > > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
> > 
> > > ---
> > >   drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 9 +++++++++
> > >   1 file changed, 9 insertions(+)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
> > > b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
> > > index a0cc34be7b56..ee5525c6f79b 100644
> > > --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
> > > +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
> > > @@ -523,6 +523,15 @@ static inline bool ct_deadlocked(struct
> > > intel_guc_ct *ct)
> > >           CT_ERROR(ct, "Communication stalled for %lld ms, desc
> > > status=%#x,%#x\n",
> > >                ktime_ms_delta(ktime_get(), ct->stall_time),
> > >                send->status, recv->status);
> > > +        CT_ERROR(ct, "H2G Space: %u\n",
> > > +             atomic_read(&ct->ctbs.send.space) * 4);
> > > +        CT_ERROR(ct, "Head: %u\n", ct->ctbs.send.desc->head);
> > > +        CT_ERROR(ct, "Tail: %u\n", ct->ctbs.send.desc->tail);
> Actually, aren't these offsets in dwords? So, scaling the dword space to
> bytes but leaving this as dwords would produce a confusing numbers.
> 

Copy + pasted from CT debugfs but yes it is slightly confusing. I'd
rather leave the head / tail in native format but I'll add info to both
the space / pointers print indicating the units.

Matt

> John.
> 
> > > +        CT_ERROR(ct, "G2H Space: %u\n",
> > > +             atomic_read(&ct->ctbs.recv.space) * 4);
> > > +        CT_ERROR(ct, "Head: %u\n", ct->ctbs.recv.desc->head);
> > > +        CT_ERROR(ct, "Tail: %u\n", ct->ctbs.recv.desc->tail);
> > > +
> > >           ct->ctbs.send.broken = true;
> > >       }
> > 
> 

  reply	other threads:[~2021-12-11  3:30 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11  0:56 [PATCH 0/7] Fix stealing guc_ids + test Matthew Brost
2021-12-11  0:56 ` [Intel-gfx] " Matthew Brost
2021-12-11  0:56 ` [PATCH 1/7] drm/i915/guc: Use correct context lock when callig clr_context_registered Matthew Brost
2021-12-11  0:56   ` [Intel-gfx] " Matthew Brost
2021-12-11  0:56 ` [PATCH 2/7] drm/i915/guc: Only assign guc_id.id when stealing guc_id Matthew Brost
2021-12-11  0:56   ` [Intel-gfx] " Matthew Brost
2021-12-11  1:08   ` John Harrison
2021-12-11  1:08     ` [Intel-gfx] " John Harrison
2021-12-11  0:56 ` [PATCH 3/7] drm/i915/guc: Remove racey GEM_BUG_ON Matthew Brost
2021-12-11  0:56   ` [Intel-gfx] " Matthew Brost
2021-12-11  0:56 ` [PATCH 4/7] drm/i915/guc: Don't hog IRQs when destroying contexts Matthew Brost
2021-12-11  0:56   ` [Intel-gfx] " Matthew Brost
2021-12-11  1:07   ` John Harrison
2021-12-11  1:07     ` [Intel-gfx] " John Harrison
2021-12-11  1:10     ` Matthew Brost
2021-12-11  1:10       ` [Intel-gfx] " Matthew Brost
2021-12-11  0:56 ` [PATCH 5/7] drm/i915/guc: Add extra debug on CT deadlock Matthew Brost
2021-12-11  0:56   ` [Intel-gfx] " Matthew Brost
2021-12-11  1:43   ` John Harrison
2021-12-11  1:43     ` [Intel-gfx] " John Harrison
2021-12-11  1:45     ` John Harrison
2021-12-11  3:24       ` Matthew Brost [this message]
2021-12-11  0:56 ` [PATCH 6/7] drm/i915/guc: Kick G2H tasklet if no credits Matthew Brost
2021-12-11  0:56   ` [Intel-gfx] " Matthew Brost
2021-12-11  0:56 ` [PATCH 7/7] drm/i915/guc: Selftest for stealing of guc ids Matthew Brost
2021-12-11  0:56   ` [Intel-gfx] " Matthew Brost
2021-12-11  1:33   ` John Harrison
2021-12-11  1:33     ` [Intel-gfx] " John Harrison
2021-12-11  3:31     ` Matthew Brost
2021-12-11  3:31       ` [Intel-gfx] " Matthew Brost
2021-12-11  3:32     ` Matthew Brost
2021-12-11  3:32       ` [Intel-gfx] " Matthew Brost
2021-12-11  2:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix stealing guc_ids + test Patchwork
2021-12-11  2:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-11  2:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-12  1:32 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-12-11 17:35 [PATCH 0/7] " Matthew Brost
2021-12-11 17:35 ` [Intel-gfx] [PATCH 5/7] drm/i915/guc: Add extra debug on CT deadlock Matthew Brost
2021-12-14 17:04 [PATCH 0/7] Fix stealing guc_ids + test Matthew Brost
2021-12-14 17:04 ` [Intel-gfx] [PATCH 5/7] drm/i915/guc: Add extra debug on CT deadlock Matthew Brost

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=20211211032457.GA8882@jons-linux-dev-box \
    --to=matthew.brost@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=john.c.harrison@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.