From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@kernel.org>,
intel-xe@lists.freedesktop.org, Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-xe] [PATCH] drm/xe: Print GT info on TLB inv failure
Date: Mon, 8 May 2023 17:21:54 -0400 [thread overview]
Message-ID: <ZFln8oZby1JaRy0i@intel.com> (raw)
In-Reply-To: <edb8a4d0-99ab-0d4c-d866-e6e6e94cd472@intel.com>
On Mon, May 08, 2023 at 11:10:25PM +0200, Michal Wajdeczko wrote:
>
>
> On 05.05.2023 15:47, Rodrigo Vivi wrote:
> > On Fri, May 05, 2023 at 03:34:33PM +0200, Nirmoy Das wrote:
> >> Print GT info on TLB inv failure for better debugbility.
> >>
> >> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> >
> > Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >
> >> ---
> >> drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 8 ++++----
> >> 1 file changed, 4 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> >> index 604f189dbd70..9e7fe8d9bca4 100644
> >> --- a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> >> +++ b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> >> @@ -34,8 +34,8 @@ static void xe_gt_tlb_fence_timeout(struct work_struct *work)
> >> break;
> >>
> >> trace_xe_gt_tlb_invalidation_fence_timeout(fence);
> >> - drm_err(>_to_xe(gt)->drm, "TLB invalidation fence timeout, seqno=%d",
> >> - fence->seqno);
> >> + drm_err(>_to_xe(gt)->drm, "gt%d: TLB invalidation fence timeout, seqno=%d",
> >> + gt->info.id, fence->seqno);
> >>
> >> list_del(&fence->link);
> >> fence->base.error = -ETIME;
> >> @@ -285,8 +285,8 @@ int xe_gt_tlb_invalidation_wait(struct xe_gt *gt, int seqno)
> >> tlb_invalidation_seqno_past(gt, seqno),
> >> TLB_TIMEOUT);
> >> if (!ret) {
> >> - drm_err(&xe->drm, "TLB invalidation time'd out, seqno=%d, recv=%d\n",
> >> - seqno, gt->tlb_invalidation.seqno_recv);
> >> + drm_err(&xe->drm, "gt%d: TLB invalidation time'd out, seqno=%d, recv=%d\n",
> >> + gt->info.id, seqno, gt->tlb_invalidation.seqno_recv);
>
> as a reminder, there is pending series with gt log wrappers [1] that
> could be used also here to avoid manual addition of "gt%u" prefix
>
> [1] https://patchwork.freedesktop.org/series/115083/
Indeed. sorry for not reacting to your v2.
After the many rebases and other patches, I believe we probably
need a rebased v2 to v3.
Then count on my rv-b there. Just cc me so I don't forget.
>
> >> return -ETIME;
> >> }
> >>
> >> --
> >> 2.39.0
> >>
next prev parent reply other threads:[~2023-05-08 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 13:34 [Intel-xe] [PATCH] drm/xe: Print GT info on TLB inv failure Nirmoy Das
2023-05-05 13:37 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-05-05 13:38 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-05 13:42 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-05 13:47 ` [Intel-xe] [PATCH] " Rodrigo Vivi
2023-05-08 21:10 ` Michal Wajdeczko
2023-05-08 21:21 ` Rodrigo Vivi [this message]
2023-05-08 21:41 ` Das, Nirmoy
2023-05-05 14:07 ` [Intel-xe] ○ CI.BAT: info for " 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=ZFln8oZby1JaRy0i@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=nirmoy.das@intel.com \
--cc=rodrigo.vivi@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 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.