Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v3 05/63] drm/i915: Ensure we hold the object mutex in pin correctly.
Date: Thu, 15 Oct 2020 13:25:29 +0200	[thread overview]
Message-ID: <20201015112627.1142745-6-maarten.lankhorst@linux.intel.com> (raw)
In-Reply-To: <20201015112627.1142745-1-maarten.lankhorst@linux.intel.com>

Currently we have a lot of places where we hold the gem object lock,
but haven't yet been converted to the ww dance. Complain loudly about
those places.

i915_vma_pin shouldn't have the obj lock held, so we can do a ww dance,
while i915_vma_pin_ww should.

Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
---
 drivers/gpu/drm/i915/gt/intel_renderstate.c |  2 +-
 drivers/gpu/drm/i915/i915_vma.c             | 11 ++++++++++-
 drivers/gpu/drm/i915/i915_vma.h             |  3 +++
 3 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/i915/gt/intel_renderstate.c b/drivers/gpu/drm/i915/gt/intel_renderstate.c
index ea2a77c7b469..a68e5c23a67c 100644
--- a/drivers/gpu/drm/i915/gt/intel_renderstate.c
+++ b/drivers/gpu/drm/i915/gt/intel_renderstate.c
@@ -196,7 +196,7 @@ int intel_renderstate_init(struct intel_renderstate *so,
 	if (err)
 		goto err_context;
 
-	err = i915_vma_pin(so->vma, 0, 0, PIN_GLOBAL | PIN_HIGH);
+	err = i915_vma_pin_ww(so->vma, &so->ww, 0, 0, PIN_GLOBAL | PIN_HIGH);
 	if (err)
 		goto err_context;
 
diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
index ffb5287e055a..4ead74c5142b 100644
--- a/drivers/gpu/drm/i915/i915_vma.c
+++ b/drivers/gpu/drm/i915/i915_vma.c
@@ -863,6 +863,8 @@ int i915_vma_pin_ww(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,
 #ifdef CONFIG_PROVE_LOCKING
 	if (debug_locks && lockdep_is_held(&vma->vm->i915->drm.struct_mutex))
 		WARN_ON(!ww);
+	if (debug_locks && ww && vma->resv)
+		assert_vma_held(vma);
 #endif
 
 	BUILD_BUG_ON(PIN_GLOBAL != I915_VMA_GLOBAL_BIND);
@@ -1018,8 +1020,15 @@ int i915_ggtt_pin(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,
 
 	GEM_BUG_ON(!i915_vma_is_ggtt(vma));
 
+#ifdef CONFIG_LOCKDEP
+	WARN_ON(!ww && vma->resv && dma_resv_held(vma->resv));
+#endif
+
 	do {
-		err = i915_vma_pin_ww(vma, ww, 0, align, flags | PIN_GLOBAL);
+		if (ww)
+			err = i915_vma_pin_ww(vma, ww, 0, align, flags | PIN_GLOBAL);
+		else
+			err = i915_vma_pin(vma, 0, align, flags | PIN_GLOBAL);
 		if (err != -ENOSPC) {
 			if (!err) {
 				err = i915_vma_wait_for_bind(vma);
diff --git a/drivers/gpu/drm/i915/i915_vma.h b/drivers/gpu/drm/i915/i915_vma.h
index 5b3a3c653454..838bbbeb11cc 100644
--- a/drivers/gpu/drm/i915/i915_vma.h
+++ b/drivers/gpu/drm/i915/i915_vma.h
@@ -243,6 +243,9 @@ i915_vma_pin_ww(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,
 static inline int __must_check
 i915_vma_pin(struct i915_vma *vma, u64 size, u64 alignment, u64 flags)
 {
+#ifdef CONFIG_LOCKDEP
+	WARN_ON_ONCE(vma->resv && dma_resv_held(vma->resv));
+#endif
 	return i915_vma_pin_ww(vma, NULL, size, alignment, flags);
 }
 
-- 
2.28.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-10-15 11:26 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 11:25 [Intel-gfx] [PATCH v3 00/63] drm/i915: Remove obj->mm.lock! Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 01/63] drm/i915: Move cmd parser pinning to execbuffer Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 02/63] drm/i915: Add missing -EDEADLK handling to execbuf pinning Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 03/63] drm/i915: Do not share hwsp across contexts any more, v3 Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 04/63] drm/i915: Pin timeline map after first timeline pin, v3 Maarten Lankhorst
2020-10-27 11:03   ` Thomas Hellström (Intel)
2020-10-27 14:31     ` Maarten Lankhorst
2020-10-27 16:25       ` Thomas Hellström (Intel)
2020-10-27 18:10         ` Thomas Hellström (Intel)
2020-10-15 11:25 ` Maarten Lankhorst [this message]
2020-10-27 11:07   ` [Intel-gfx] [PATCH v3 05/63] drm/i915: Ensure we hold the object mutex in pin correctly Thomas Hellström (Intel)
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 06/63] drm/i915: Add gem object locking to madvise Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 07/63] drm/i915: Move HAS_STRUCT_PAGE to obj->flags Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 08/63] drm/i915: Rework struct phys attachment handling Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 09/63] drm/i915: Convert i915_gem_object_attach_phys() to ww locking Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 10/63] drm/i915: make lockdep slightly happier about execbuf Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 11/63] drm/i915: Disable userptr pread/pwrite support Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 12/63] drm/i915: No longer allow exporting userptr through dma-buf Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 13/63] drm/i915: Reject more ioctls for userptr Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 14/63] drm/i915: Reject UNSYNCHRONIZED " Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 15/63] drm/i915: Fix userptr so we do not have to worry about obj->mm.lock, v3 Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 16/63] drm/i915: Flatten obj->mm.lock Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 17/63] drm/i915: Populate logical context during first pin Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 18/63] drm/i915: Make ring submission compatible with obj->mm.lock removal, v2 Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 19/63] drm/i915: Handle ww locking in init_status_page Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 20/63] drm/i915: Rework clflush to work correctly without obj->mm.lock Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 21/63] drm/i915: Pass ww ctx to intel_pin_to_display_plane Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 22/63] drm/i915: Add object locking to vm_fault_cpu Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 23/63] drm/i915: Move pinning to inside engine_wa_list_verify() Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 24/63] drm/i915: Take reservation lock around i915_vma_pin Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 25/63] drm/i915: Make intel_init_workaround_bb more compatible with ww locking Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 26/63] drm/i915: Make __engine_unpark() " Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 27/63] drm/i915: Take obj lock around set_domain ioctl Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 28/63] drm/i915: Defer pin calls in buffer pool until first use by caller Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 29/63] drm/i915: Fix pread/pwrite to work with new locking rules Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 30/63] drm/i915: Fix workarounds selftest, part 1 Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 31/63] drm/i915: Prepare for obj->mm.lock removal Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 32/63] drm/i915: Add igt_spinner_pin() to allow for ww locking around spinner Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 33/63] drm/i915: Add ww locking around vm_access() Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 34/63] drm/i915: Increase ww locking for perf Maarten Lankhorst
2020-10-15 11:25 ` [Intel-gfx] [PATCH v3 35/63] drm/i915: Lock ww in ucode objects correctly Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 36/63] drm/i915: Add ww locking to dma-buf ops Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 37/63] drm/i915: Add missing ww lock in intel_dsb_prepare Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 38/63] drm/i915: Fix ww locking in shmem_create_from_object Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 39/63] drm/i915: Use a single page table lock for each gtt Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 40/63] drm/i915/selftests: Prepare huge_pages testcases for obj->mm.lock removal Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 41/63] drm/i915/selftests: Prepare client blit " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 42/63] drm/i915/selftests: Prepare coherency tests " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 43/63] drm/i915/selftests: Prepare context " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 44/63] drm/i915/selftests: Prepare dma-buf " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 45/63] drm/i915/selftests: Prepare execbuf " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 46/63] drm/i915/selftests: Prepare mman testcases " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 47/63] drm/i915/selftests: Prepare object tests " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 48/63] drm/i915/selftests: Prepare object blit " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 49/63] drm/i915/selftests: Prepare igt_gem_utils " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 50/63] drm/i915/selftests: Prepare context selftest " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 51/63] drm/i915/selftests: Prepare hangcheck " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 52/63] drm/i915/selftests: Prepare execlists " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 53/63] drm/i915/selftests: Prepare mocs tests " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 54/63] drm/i915/selftests: Prepare ring submission " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 55/63] drm/i915/selftests: Prepare timeline tests " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 56/63] drm/i915/selftests: Prepare i915_request " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 57/63] drm/i915/selftests: Prepare memory region " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 58/63] drm/i915/selftests: Prepare cs engine " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 59/63] drm/i915/selftests: Prepare gtt " Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 60/63] drm/i915: Finally remove obj->mm.lock Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 61/63] drm/i915: Keep userpointer bindings if seqcount is unchanged, v2 Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 62/63] drm/i915: Idea to implement eviction locking Maarten Lankhorst
2020-10-15 11:26 ` [Intel-gfx] [PATCH v3 63/63] drm/i915: Keep lazy reference to userptr pages Maarten Lankhorst
2020-10-15 13:23 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Remove obj->mm.lock! (rev3) Patchwork
2020-10-15 13:24 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-10-15 13:27 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2020-10-15 13:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-10-15 17:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=20201015112627.1142745-6-maarten.lankhorst@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=intel-gfx@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