Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH v6 06/11] drm/xe/ct: serialise fast_lock during CT disable
Date: Mon, 10 Jul 2023 10:40:44 +0100	[thread overview]
Message-ID: <20230710094037.28179-19-matthew.auld@intel.com> (raw)
In-Reply-To: <20230710094037.28179-13-matthew.auld@intel.com>

The fast-path CT could be running as we enter a runtime-suspend or
potentially a GT reset, however here we only use the ct->fast_lock and
not the full ct->lock. Before disabling the CT, also serialise against
the fast_lock to ensure any in-progress work finishes before we start
nuking the CT related stuff. Once we disable ct->enabled and drop the
lock, any new work should fail gracefully, and anything that was in
progress should be finished.

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>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
---
 drivers/gpu/drm/xe/xe_guc_ct.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
index ba89db1dcfdb..acf488b00b66 100644
--- a/drivers/gpu/drm/xe/xe_guc_ct.c
+++ b/drivers/gpu/drm/xe/xe_guc_ct.c
@@ -301,8 +301,10 @@ int xe_guc_ct_enable(struct xe_guc_ct *ct)
 		goto err_out;
 
 	mutex_lock(&ct->lock);
+	spin_lock_irq(&ct->fast_lock);
 	ct->g2h_outstanding = 0;
 	ct->enabled = true;
+	spin_unlock_irq(&ct->fast_lock);
 	mutex_unlock(&ct->lock);
 
 	smp_mb();
@@ -319,8 +321,10 @@ int xe_guc_ct_enable(struct xe_guc_ct *ct)
 
 void xe_guc_ct_disable(struct xe_guc_ct *ct)
 {
-	mutex_lock(&ct->lock);
-	ct->enabled = false;
+	mutex_lock(&ct->lock); /* Serialise dequeue_one_g2h() */
+	spin_lock_irq(&ct->fast_lock); /* Serialise CT fast-path */
+	ct->enabled = false; /* Finally disable CT communication */
+	spin_unlock_irq(&ct->fast_lock);
 	mutex_unlock(&ct->lock);
 
 	xa_destroy(&ct->fence_lookup);
-- 
2.41.0


  parent reply	other threads:[~2023-07-10  9:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  9:40 [Intel-xe] [PATCH v6 00/11] Try to handle TLB invalidations from CT fast-path Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 01/11] drm/xe/tlb: drop unnecessary smp_wmb() Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 02/11] drm/xe/tlb: ensure we access seqno_recv once Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 03/11] drm/xe: hold mem_access.ref for CT fast-path Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 04/11] drm/xe/ct: hold fast_lock when reserving space for g2h Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 05/11] drm/xe/tlb: increment next seqno after successful CT send Matthew Auld
2023-07-10  9:40 ` Matthew Auld [this message]
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 07/11] drm/xe/gt: tweak placement for signalling TLB fences after GT reset Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 08/11] drm/xe/tlb: also update seqno_recv during reset Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 09/11] drm/xe/tlb: print seqno_recv on fence TLB timeout Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 10/11] drm/xe/ct: update g2h outstanding for CTB capture Matthew Auld
2023-07-10 13:42   ` Matthew Brost
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 11/11] drm/xe: handle TLB invalidations from CT fast-path Matthew Auld
2023-07-10 10:13 ` [Intel-xe] ✓ CI.Patch_applied: success for Try to handle TLB invalidations from CT fast-path (rev4) Patchwork
2023-07-10 10:13 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-10 10:15 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-10 10:19 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-10 10:19 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-10 10:20 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-10 11:06 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-07-10 14:41 ` [Intel-xe] [PATCH v6 00/11] Try to handle TLB invalidations from CT fast-path 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=20230710094037.28179-19-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