From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v2 34/61] drm/i915: Increase ww locking for perf.
Date: Mon, 12 Oct 2020 16:46:39 +0200 [thread overview]
Message-ID: <20201012144706.555345-35-maarten.lankhorst@linux.intel.com> (raw)
In-Reply-To: <20201012144706.555345-1-maarten.lankhorst@linux.intel.com>
We need to lock a few more objects, some temporarily,
add ww lock where needed.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
---
drivers/gpu/drm/i915/i915_perf.c | 56 ++++++++++++++++++++++++--------
1 file changed, 43 insertions(+), 13 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
index e94976976571..281af1fdf514 100644
--- a/drivers/gpu/drm/i915/i915_perf.c
+++ b/drivers/gpu/drm/i915/i915_perf.c
@@ -1579,7 +1579,7 @@ static int alloc_oa_buffer(struct i915_perf_stream *stream)
stream->oa_buffer.vma = vma;
stream->oa_buffer.vaddr =
- i915_gem_object_pin_map(bo, I915_MAP_WB);
+ i915_gem_object_pin_map_unlocked(bo, I915_MAP_WB);
if (IS_ERR(stream->oa_buffer.vaddr)) {
ret = PTR_ERR(stream->oa_buffer.vaddr);
goto err_unpin;
@@ -1632,6 +1632,7 @@ static int alloc_noa_wait(struct i915_perf_stream *stream)
const u32 base = stream->engine->mmio_base;
#define CS_GPR(x) GEN8_RING_CS_GPR(base, x)
u32 *batch, *ts0, *cs, *jump;
+ struct i915_gem_ww_ctx ww;
int ret, i;
enum {
START_TS,
@@ -1649,15 +1650,21 @@ static int alloc_noa_wait(struct i915_perf_stream *stream)
return PTR_ERR(bo);
}
+ i915_gem_ww_ctx_init(&ww, true);
+retry:
+ ret = i915_gem_object_lock(bo, &ww);
+ if (ret)
+ goto out_ww;
+
/*
* We pin in GGTT because we jump into this buffer now because
* multiple OA config BOs will have a jump to this address and it
* needs to be fixed during the lifetime of the i915/perf stream.
*/
- vma = i915_gem_object_ggtt_pin(bo, NULL, 0, 0, PIN_HIGH);
+ vma = i915_gem_object_ggtt_pin_ww(bo, &ww, NULL, 0, 0, PIN_HIGH);
if (IS_ERR(vma)) {
ret = PTR_ERR(vma);
- goto err_unref;
+ goto out_ww;
}
batch = cs = i915_gem_object_pin_map(bo, I915_MAP_WB);
@@ -1791,12 +1798,19 @@ static int alloc_noa_wait(struct i915_perf_stream *stream)
__i915_gem_object_release_map(bo);
stream->noa_wait = vma;
- return 0;
+ goto out_ww;
err_unpin:
i915_vma_unpin_and_release(&vma, 0);
-err_unref:
- i915_gem_object_put(bo);
+out_ww:
+ if (ret == -EDEADLK) {
+ ret = i915_gem_ww_ctx_backoff(&ww);
+ if (!ret)
+ goto retry;
+ }
+ i915_gem_ww_ctx_fini(&ww);
+ if (ret)
+ i915_gem_object_put(bo);
return ret;
}
@@ -1839,6 +1853,7 @@ alloc_oa_config_buffer(struct i915_perf_stream *stream,
{
struct drm_i915_gem_object *obj;
struct i915_oa_config_bo *oa_bo;
+ struct i915_gem_ww_ctx ww;
size_t config_length = 0;
u32 *cs;
int err;
@@ -1859,10 +1874,16 @@ alloc_oa_config_buffer(struct i915_perf_stream *stream,
goto err_free;
}
+ i915_gem_ww_ctx_init(&ww, true);
+retry:
+ err = i915_gem_object_lock(obj, &ww);
+ if (err)
+ goto out_ww;
+
cs = i915_gem_object_pin_map(obj, I915_MAP_WB);
if (IS_ERR(cs)) {
err = PTR_ERR(cs);
- goto err_oa_bo;
+ goto out_ww;
}
cs = write_cs_mi_lri(cs,
@@ -1890,19 +1911,28 @@ alloc_oa_config_buffer(struct i915_perf_stream *stream,
NULL);
if (IS_ERR(oa_bo->vma)) {
err = PTR_ERR(oa_bo->vma);
- goto err_oa_bo;
+ goto out_ww;
}
oa_bo->oa_config = i915_oa_config_get(oa_config);
llist_add(&oa_bo->node, &stream->oa_config_bos);
- return oa_bo;
+out_ww:
+ if (err == -EDEADLK) {
+ err = i915_gem_ww_ctx_backoff(&ww);
+ if (!err)
+ goto retry;
+ }
+ i915_gem_ww_ctx_fini(&ww);
-err_oa_bo:
- i915_gem_object_put(obj);
+ if (err)
+ i915_gem_object_put(obj);
err_free:
- kfree(oa_bo);
- return ERR_PTR(err);
+ if (err) {
+ kfree(oa_bo);
+ return ERR_PTR(err);
+ }
+ return oa_bo;
}
static struct i915_vma *
--
2.28.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-10-12 14:48 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:46 [Intel-gfx] [PATCH v2 00/61] drm/i915: Remove obj->mm.lock! Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 01/61] drm/i915: Move cmd parser pinning to execbuffer Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 02/61] drm/i915: Add missing -EDEADLK handling to execbuf pinning Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 03/61] drm/i915: Do not share hwsp across contexts any more, v3 Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 04/61] drm/i915: Ensure we hold the object mutex in pin correctly Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 05/61] drm/i915: Add gem object locking to madvise Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 06/61] drm/i915: Move HAS_STRUCT_PAGE to obj->flags Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 07/61] drm/i915: Rework struct phys attachment handling Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 08/61] drm/i915: Convert i915_gem_object_attach_phys() to ww locking Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 09/61] drm/i915: make lockdep slightly happier about execbuf Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 10/61] drm/i915: Disable userptr pread/pwrite support Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 11/61] drm/i915: No longer allow exporting userptr through dma-buf Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 12/61] drm/i915: Reject more ioctls for userptr Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 13/61] drm/i915: Reject UNSYNCHRONIZED " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 14/61] drm/i915: Fix userptr so we do not have to worry about obj->mm.lock, v2 Maarten Lankhorst
2020-10-12 17:05 ` Thomas Hellström (Intel)
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 15/61] drm/i915: Flatten obj->mm.lock Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 16/61] drm/i915: Pin timeline map after first timeline pin, v2 Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 17/61] drm/i915: Populate logical context during first pin Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 18/61] drm/i915: Make ring submission compatible with obj->mm.lock removal, v2 Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 19/61] drm/i915: Handle ww locking in init_status_page Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 20/61] drm/i915: Rework clflush to work correctly without obj->mm.lock Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 21/61] drm/i915: Pass ww ctx to intel_pin_to_display_plane Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 22/61] drm/i915: Add object locking to vm_fault_cpu Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 23/61] drm/i915: Move pinning to inside engine_wa_list_verify() Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 24/61] drm/i915: Take reservation lock around i915_vma_pin Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 25/61] drm/i915: Make intel_init_workaround_bb more compatible with ww locking Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 26/61] drm/i915: Make __engine_unpark() " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 27/61] drm/i915: Take obj lock around set_domain ioctl Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 28/61] drm/i915: Defer pin calls in buffer pool until first use by caller Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 29/61] drm/i915: Fix pread/pwrite to work with new locking rules Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 30/61] drm/i915: Fix workarounds selftest, part 1 Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 31/61] drm/i915: Prepare for obj->mm.lock removal Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 32/61] drm/i915: Add igt_spinner_pin() to allow for ww locking around spinner Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 33/61] drm/i915: Add ww locking around vm_access() Maarten Lankhorst
2020-10-12 14:46 ` Maarten Lankhorst [this message]
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 35/61] drm/i915: Lock ww in ucode objects correctly Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 36/61] drm/i915: Add ww locking to dma-buf ops Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 37/61] drm/i915: Add missing ww lock in intel_dsb_prepare Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 38/61] drm/i915: Fix ww locking in shmem_create_from_object Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 39/61] drm/i915: Use a single page table lock for each gtt Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 40/61] drm/i915/selftests: Prepare huge_pages testcases for obj->mm.lock removal Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 41/61] drm/i915/selftests: Prepare client blit " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 42/61] drm/i915/selftests: Prepare coherency tests " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 43/61] drm/i915/selftests: Prepare context " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 44/61] drm/i915/selftests: Prepare dma-buf " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 45/61] drm/i915/selftests: Prepare execbuf " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 46/61] drm/i915/selftests: Prepare mman testcases " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 47/61] drm/i915/selftests: Prepare object tests " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 48/61] drm/i915/selftests: Prepare object blit " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 49/61] drm/i915/selftests: Prepare igt_gem_utils " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 50/61] drm/i915/selftests: Prepare context selftest " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 51/61] drm/i915/selftests: Prepare hangcheck " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 52/61] drm/i915/selftests: Prepare execlists " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 53/61] drm/i915/selftests: Prepare mocs tests " Maarten Lankhorst
2020-10-12 14:46 ` [Intel-gfx] [PATCH v2 54/61] drm/i915/selftests: Prepare ring submission " Maarten Lankhorst
2020-10-12 14:47 ` [Intel-gfx] [PATCH v2 55/61] drm/i915/selftests: Prepare timeline tests " Maarten Lankhorst
2020-10-12 14:47 ` [Intel-gfx] [PATCH v2 56/61] drm/i915/selftests: Prepare i915_request " Maarten Lankhorst
2020-10-12 14:47 ` [Intel-gfx] [PATCH v2 57/61] drm/i915/selftests: Prepare memory region " Maarten Lankhorst
2020-10-12 14:47 ` [Intel-gfx] [PATCH v2 58/61] drm/i915/selftests: Prepare cs engine " Maarten Lankhorst
2020-10-12 14:47 ` [Intel-gfx] [PATCH v2 59/61] drm/i915/selftests: Prepare gtt " Maarten Lankhorst
2020-10-12 14:47 ` [Intel-gfx] [PATCH v2 60/61] drm/i915: Finally remove obj->mm.lock Maarten Lankhorst
2020-10-12 14:47 ` [Intel-gfx] [PATCH v2 61/61] drm/i915: Keep userpointer bindings if seqcount is unchanged Maarten Lankhorst
2020-10-12 16:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Remove obj->mm.lock! (rev2) Patchwork
2020-10-12 16:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-10-12 16:49 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2020-10-12 17:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-10-12 19:57 ` [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=20201012144706.555345-35-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