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
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH] drm/xe/preempt_fence: enlarge the fence critical section
Date: Thu, 18 Apr 2024 15:46:31 +0100	[thread overview]
Message-ID: <20240418144630.299531-2-matthew.auld@intel.com> (raw)

It is really easy to introduce subtle deadlocks in
preempt_fence_work_func() since we operate on single global ordered-wq
for signalling our preempt fences behind the scenes, so even though we
signal a particular fence, everything in the callback should be in the
fence critical section, since blocking in the callback will prevent
other published fences from signalling. If we enlarge the fence critical
section to cover the entire callback, then lockdep should be able to
understand this better, and complain if we grab a sensitive lock like
vm->lock, which is also held when waiting on preempt fences.

Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
---
 drivers/gpu/drm/xe/xe_preempt_fence.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_preempt_fence.c b/drivers/gpu/drm/xe/xe_preempt_fence.c
index 7d50c6e89d8e..5b243b7feb59 100644
--- a/drivers/gpu/drm/xe/xe_preempt_fence.c
+++ b/drivers/gpu/drm/xe/xe_preempt_fence.c
@@ -23,11 +23,19 @@ static void preempt_fence_work_func(struct work_struct *w)
 		q->ops->suspend_wait(q);
 
 	dma_fence_signal(&pfence->base);
-	dma_fence_end_signalling(cookie);
-
+	/*
+	 * Opt for keep everything in the fence critical section. This looks really strange since we
+	 * have just signalled the fence, however the preempt fences are all signalled via single
+	 * global ordered-wq, therefore anything that happens in this callback can easily block
+	 * progress on the entire wq, which itself may prevent other published preempt fences from
+	 * ever signalling.  Therefore try to keep everything here in the callback in the fence
+	 * critical section. For example if something below grabs a scary lock like vm->lock,
+	 * lockdep should complain since we also hold that lock whilst waiting on preempt fences to
+	 * complete.
+	 */
 	xe_vm_queue_rebind_worker(q->vm);
-
 	xe_exec_queue_put(q);
+	dma_fence_end_signalling(cookie);
 }
 
 static const char *
-- 
2.44.0


             reply	other threads:[~2024-04-18 14:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 14:46 Matthew Auld [this message]
2024-04-18 18:06 ` ✓ CI.Patch_applied: success for drm/xe/preempt_fence: enlarge the fence critical section Patchwork
2024-04-18 18:06 ` ✓ CI.checkpatch: " Patchwork
2024-04-18 18:11 ` ✓ CI.KUnit: " Patchwork
2024-04-18 18:22 ` ✓ CI.Build: " Patchwork
2024-04-18 18:32 ` ✓ CI.Hooks: " Patchwork
2024-04-18 18:35 ` ✓ CI.checksparse: " Patchwork
2024-04-18 19:40 ` ✗ CI.BAT: failure " Patchwork
2024-04-18 19:55 ` [PATCH] " Matthew Brost
2024-04-19  7:44   ` Matthew Auld
2024-04-19  7:43 ` ✓ CI.Patch_applied: success for drm/xe/preempt_fence: enlarge the fence critical section (rev2) Patchwork
2024-04-19  7:43 ` ✓ CI.checkpatch: " Patchwork
2024-04-19  7:45 ` ✓ CI.KUnit: " Patchwork
2024-04-19  7:57 ` ✓ CI.Build: " Patchwork
2024-04-19  8:00 ` ✓ CI.Hooks: " Patchwork
2024-04-19  8:01 ` ✓ CI.checksparse: " Patchwork
2024-04-19  8:31 ` ✓ CI.BAT: " Patchwork
2024-04-20  9:54 ` ✗ CI.FULL: failure for drm/xe/preempt_fence: enlarge the fence critical section Patchwork
2024-04-21  0:50 ` ✓ CI.FULL: success for drm/xe/preempt_fence: enlarge the fence critical section (rev2) 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=20240418144630.299531-2-matthew.auld@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox