From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
linaro-mm-sig@lists.linaro.org, dri-devel@lists.freedesktop.org,
linux-media@vger.kernel.org, intel-gfx@lists.freedesktop.org
Cc: daniel@ffwll.ch
Subject: Re: [Intel-gfx] [PATCH 17/28] drm/i915: use the new iterator in i915_gem_busy_ioctl v2
Date: Tue, 5 Oct 2021 14:44:50 +0200 [thread overview]
Message-ID: <65e28697-6f0a-7f97-d49b-ebf8d0b8d23f@gmail.com> (raw)
In-Reply-To: <50b8ffb7-2720-619d-3140-af2f90450a21@linux.intel.com>
Am 05.10.21 um 14:40 schrieb Tvrtko Ursulin:
>
> On 05/10/2021 12:37, Christian König wrote:
>> This makes the function much simpler since the complex
>> retry logic is now handled else where.
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Reminder - r-b was retracted until at least more text is added to
> commit message about pros and cons. But really some discussion had
> inside the i915 team on the topic.
Sure, going to move those to a different branch.
But I really only see the following options:
1. Grab the lock.
2. Use the _unlocked variant with get/put.
3. Add another _rcu iterator just for this case.
I'm fine with either, but Daniel pretty much already rejected #3 and
#2/#1 has more overhead then the original one.
Regards,
Christian.
>
> Regards,
>
> Tvrtko
>
>> ---
>> drivers/gpu/drm/i915/gem/i915_gem_busy.c | 35 ++++++++++--------------
>> 1 file changed, 14 insertions(+), 21 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_busy.c
>> b/drivers/gpu/drm/i915/gem/i915_gem_busy.c
>> index 6234e17259c1..dc72b36dae54 100644
>> --- a/drivers/gpu/drm/i915/gem/i915_gem_busy.c
>> +++ b/drivers/gpu/drm/i915/gem/i915_gem_busy.c
>> @@ -82,8 +82,8 @@ i915_gem_busy_ioctl(struct drm_device *dev, void
>> *data,
>> {
>> struct drm_i915_gem_busy *args = data;
>> struct drm_i915_gem_object *obj;
>> - struct dma_resv_list *list;
>> - unsigned int seq;
>> + struct dma_resv_iter cursor;
>> + struct dma_fence *fence;
>> int err;
>> err = -ENOENT;
>> @@ -109,27 +109,20 @@ i915_gem_busy_ioctl(struct drm_device *dev,
>> void *data,
>> * to report the overall busyness. This is what the wait-ioctl
>> does.
>> *
>> */
>> -retry:
>> - seq = raw_read_seqcount(&obj->base.resv->seq);
>> -
>> - /* Translate the exclusive fence to the READ *and* WRITE engine */
>> - args->busy =
>> busy_check_writer(dma_resv_excl_fence(obj->base.resv));
>> -
>> - /* Translate shared fences to READ set of engines */
>> - list = dma_resv_shared_list(obj->base.resv);
>> - if (list) {
>> - unsigned int shared_count = list->shared_count, i;
>> -
>> - for (i = 0; i < shared_count; ++i) {
>> - struct dma_fence *fence =
>> - rcu_dereference(list->shared[i]);
>> -
>> + args->busy = 0;
>> + dma_resv_iter_begin(&cursor, obj->base.resv, true);
>> + dma_resv_for_each_fence_unlocked(&cursor, fence) {
>> + if (dma_resv_iter_is_restarted(&cursor))
>> + args->busy = 0;
>> +
>> + if (dma_resv_iter_is_exclusive(&cursor))
>> + /* Translate the exclusive fence to the READ *and* WRITE
>> engine */
>> + args->busy |= busy_check_writer(fence);
>> + else
>> + /* Translate shared fences to READ set of engines */
>> args->busy |= busy_check_reader(fence);
>> - }
>> }
>> -
>> - if (args->busy && read_seqcount_retry(&obj->base.resv->seq, seq))
>> - goto retry;
>> + dma_resv_iter_end(&cursor);
>> err = 0;
>> out:
>>
next prev parent reply other threads:[~2021-10-05 12:46 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 11:37 [Intel-gfx] Deploying new iterator interface for dma-buf Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 01/28] dma-buf: add dma_resv_for_each_fence_unlocked v8 Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 02/28] dma-buf: add dma_resv_for_each_fence v2 Christian König
2021-10-06 8:24 ` Christian König
2021-10-06 8:40 ` Tvrtko Ursulin
2021-10-06 8:52 ` Tvrtko Ursulin
2021-10-05 11:37 ` [Intel-gfx] [PATCH 03/28] dma-buf: add dma_resv selftest v3 Christian König
2021-10-13 14:04 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 04/28] dma-buf: use new iterator in dma_resv_copy_fences Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 05/28] dma-buf: use new iterator in dma_resv_get_fences v3 Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 06/28] dma-buf: use new iterator in dma_resv_wait_timeout Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 07/28] dma-buf: use new iterator in dma_resv_test_signaled Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 08/28] dma-buf: use the new iterator in dma_buf_debug_show Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 09/28] dma-buf: use the new iterator in dma_resv_poll Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 10/28] drm/ttm: use the new iterator in ttm_bo_flush_all_fences Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 11/28] drm/amdgpu: use the new iterator in amdgpu_sync_resv Christian König
2021-10-13 14:06 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 12/28] drm/amdgpu: use new iterator in amdgpu_ttm_bo_eviction_valuable Christian König
2021-10-13 14:07 ` Daniel Vetter
2021-10-19 11:36 ` Christian König
2021-10-19 16:30 ` Felix Kuehling
2021-10-21 11:29 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 13/28] drm/amdgpu: use new iterator in amdgpu_vm_prt_fini Christian König
2021-10-13 14:12 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 14/28] drm/msm: use new iterator in msm_gem_describe Christian König
2021-10-13 14:14 ` Daniel Vetter
2021-10-19 11:49 ` Christian König
2021-10-21 11:30 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 15/28] drm/radeon: use new iterator in radeon_sync_resv Christian König
2021-10-13 14:15 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 16/28] drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2 Christian König
2021-10-17 14:40 ` Nicolas Frattaroli
2021-10-17 15:26 ` Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 17/28] drm/i915: use the new iterator in i915_gem_busy_ioctl v2 Christian König
2021-10-05 12:40 ` Tvrtko Ursulin
2021-10-05 12:44 ` Christian König [this message]
2021-10-13 14:19 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 18/28] drm/i915: use the new iterator in i915_sw_fence_await_reservation v3 Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 19/28] drm/i915: use the new iterator in i915_request_await_object v2 Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 20/28] drm/i915: use new iterator in i915_gem_object_wait_reservation Christian König
2021-10-14 12:04 ` Maarten Lankhorst
2021-10-05 11:37 ` [Intel-gfx] [PATCH 21/28] drm/i915: use new iterator in i915_gem_object_wait_priority Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 22/28] drm/i915: use new cursor in intel_prepare_plane_fb Christian König
2021-10-05 11:37 ` [Intel-gfx] [PATCH 23/28] drm: use new iterator in drm_gem_fence_array_add_implicit v3 Christian König
2021-10-13 14:21 ` Daniel Vetter
2021-10-19 12:54 ` Christian König
2021-10-19 13:59 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 24/28] drm: use new iterator in drm_gem_plane_helper_prepare_fb v2 Christian König
2021-10-13 14:23 ` Daniel Vetter
2021-10-19 13:02 ` Christian König
2021-10-19 14:30 ` Daniel Vetter
2021-10-19 15:51 ` Christian König
2021-10-21 11:31 ` Daniel Vetter
2021-10-21 11:33 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 25/28] drm/nouveau: use the new iterator in nouveau_fence_sync Christian König
2021-10-13 14:27 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 26/28] drm/nouveau: use the new interator in nv50_wndw_prepare_fb Christian König
2021-10-13 14:29 ` Daniel Vetter
2021-10-22 13:17 ` Christian König
2021-10-28 15:26 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 27/28] drm/etnaviv: use new iterator in etnaviv_gem_describe Christian König
2021-10-13 14:31 ` Daniel Vetter
2021-10-05 11:37 ` [Intel-gfx] [PATCH 28/28] drm/etnaviv: replace dma_resv_get_excl_unlocked Christian König
2021-10-13 14:32 ` Daniel Vetter
2021-10-05 13:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/28] dma-buf: add dma_resv_for_each_fence_unlocked v8 Patchwork
2021-10-05 13:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-10-05 14:01 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-10-01 10:05 [Intel-gfx] Deploying new iterator interface for dma-buf Christian König
2021-10-01 10:05 ` [Intel-gfx] [PATCH 17/28] drm/i915: use the new iterator in i915_gem_busy_ioctl v2 Christian König
2021-10-01 10:37 ` Tvrtko Ursulin
2021-10-01 10:39 ` Christian König
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=65e28697-6f0a-7f97-d49b-ebf8d0b8d23f@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=tvrtko.ursulin@linux.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