From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2 6/8] drm/xe: Include GT ID in error message if TLB invalidation times out
Date: Tue, 9 May 2023 13:37:26 +0200 [thread overview]
Message-ID: <eecbd993-4464-aa21-0440-d0bb37333293@linux.intel.com> (raw)
In-Reply-To: <20230412225248.3229571-7-matthew.d.roper@intel.com>
I missed it. I have sent a very similar patch which now merged.
Tried this series on a MTL and I can confirm it fixes driver load.
On 4/13/2023 12:52 AM, Matt Roper wrote:
> This will hopefully help debug TLB invalidation problems.
>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> index f279e21300aa..796403b82531 100644
> --- a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> +++ b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> @@ -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, "TLB invalidation time'd out on GT%d, seqno=%d, recv=%d\n",
> + gt->info.id, seqno, gt->tlb_invalidation.seqno_recv);
> return -ETIME;
> }
>
next prev parent reply other threads:[~2023-05-09 11:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 22:52 [Intel-xe] [PATCH v2 0/8] Meteorlake interrupt & TLB handling updates Matt Roper
2023-04-12 22:52 ` [Intel-xe] [PATCH v2 1/8] drm/xe/irq: Cleanup media GT interrupt flow Matt Roper
2023-04-14 19:04 ` Lucas De Marchi
2023-04-17 17:33 ` Matt Roper
2023-04-17 21:41 ` Andi Shyti
2023-04-12 22:52 ` [Intel-xe] [PATCH v2 2/8] drm/xe/irq: Improve warnings and assertions for GT handling Matt Roper
2023-04-14 19:52 ` Lucas De Marchi
2023-04-12 22:52 ` [Intel-xe] [PATCH v2 3/8] drm/xe/irq: Process Gunit interrupts in relation to the device Matt Roper
2023-04-14 19:59 ` Lucas De Marchi
2023-04-12 22:52 ` [Intel-xe] [PATCH v2 4/8] drm/xe: Fix xe_mmio_rmw32 operation Matt Roper
2023-04-13 10:49 ` Maarten Lankhorst
2023-04-13 12:38 ` Jani Nikula
2023-04-14 1:01 ` Lucas De Marchi
2023-04-12 22:52 ` [Intel-xe] [PATCH v2 5/8] drm/xe/irq: Ensure primary GuC won't clobber media GuC's interrupt mask Matt Roper
2023-04-14 20:50 ` Lucas De Marchi
2023-04-12 22:52 ` [Intel-xe] [PATCH v2 6/8] drm/xe: Include GT ID in error message if TLB invalidation times out Matt Roper
2023-04-14 20:50 ` Lucas De Marchi
2023-05-09 11:37 ` Das, Nirmoy [this message]
2023-04-12 22:52 ` [Intel-xe] [PATCH v2 7/8] drm/xe: Invalidate TLB on all affected GTs during GGTT updates Matt Roper
2023-04-14 21:09 ` Lucas De Marchi
2023-04-14 21:22 ` Lucas De Marchi
2023-04-12 22:52 ` [Intel-xe] [PATCH v2 8/8] drm/xe/tlb: Obtain forcewake when doing GGTT TLB invalidations Matt Roper
2023-04-14 21:33 ` Lucas De Marchi
2023-04-12 22:59 ` [Intel-xe] [PATCH v2 0/8] Meteorlake interrupt & TLB handling updates Matt Roper
2023-04-12 23:01 ` Lucas De Marchi
2023-04-13 9:47 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-04-13 9:48 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-04-13 9:52 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-04-13 10:12 ` [Intel-xe] ○ CI.BAT: info " 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=eecbd993-4464-aa21-0440-d0bb37333293@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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.