From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH v3 4/5] drm/xe/tlb: also update seqno_recv during reset
Date: Tue, 4 Jul 2023 14:45:29 +0100 [thread overview]
Message-ID: <20230704134524.138377-11-matthew.auld@intel.com> (raw)
In-Reply-To: <20230704134524.138377-7-matthew.auld@intel.com>
We might have various kworkers waiting for TLB flushes to complete which
are not tracked with an explicit TLB fence, however at this stage that
will never happen since the CT is already disabled, so make sure we
signal them here under the assumption that we have completed a full GT
reset.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: José Roberto de Souza <jose.souza@intel.com>
---
drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
index 2fcb477604e2..a8f3b1b76fc5 100644
--- a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
+++ b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
@@ -89,10 +89,26 @@ invalidation_fence_signal(struct xe_gt_tlb_invalidation_fence *fence)
void xe_gt_tlb_invalidation_reset(struct xe_gt *gt)
{
struct xe_gt_tlb_invalidation_fence *fence, *next;
+ struct xe_guc *guc = >->uc.guc;
+ /*
+ * CT channel is already disabled at this point. No new TLB requests can
+ * appear.
+ */
+
+ mutex_lock(>->uc.guc.ct.lock);
cancel_delayed_work(>->tlb_invalidation.fence_tdr);
+ /*
+ * We might have various kworkers waiting for TLB flushes to complete
+ * which are not tracked with an explicit TLB fence, however at this
+ * stage that will never happen since the CT is already disabled, so
+ * make sure we signal them here under the assumption that we have
+ * completed a full GT reset.
+ */
+ gt->tlb_invalidation.seqno_recv = gt->tlb_invalidation.seqno;
+ smp_wmb();
+ wake_up_all(&guc->ct.wq);
- mutex_lock(>->uc.guc.ct.lock);
list_for_each_entry_safe(fence, next,
>->tlb_invalidation.pending_fences, link)
invalidation_fence_signal(fence);
--
2.41.0
next prev parent reply other threads:[~2023-07-04 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 13:45 [Intel-xe] [PATCH v3 0/5] Try to handle TLB invalidations from CT fast-path Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 1/5] drm/xe: hold mem_access.ref for " Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 2/5] drm/xe/ct: serialise fast_lock during CT disable Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 3/5] drm/xe/gt: tweak placement for signalling TLB fences after GT reset Matthew Auld
2023-07-04 13:45 ` Matthew Auld [this message]
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 5/5] drm/xe: handle TLB invalidations from CT fast-path Matthew Auld
2023-07-04 13:48 ` [Intel-xe] ✓ CI.Patch_applied: success for Try to " Patchwork
2023-07-04 13:49 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-04 13:50 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-04 13:54 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-04 13:54 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-04 13:55 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-04 14:42 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-07-04 18:19 ` [Intel-xe] [PATCH v3 0/5] " Souza, Jose
2023-07-04 18:42 ` Souza, Jose
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=20230704134524.138377-11-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox