From: "Das, Nirmoy" <nirmoy.das@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, <intel-gfx@lists.freedesktop.org>
Cc: thomas.hellstrom@intel.com, chris.p.wilson@intel.com
Subject: Re: [Intel-gfx] [PATCH v6] drm/i915: Individualize fences before adding to dma_resv obj
Date: Fri, 27 May 2022 12:24:30 +0200 [thread overview]
Message-ID: <4c0e1483-607c-5f0c-6085-1d94fcf60736@intel.com> (raw)
In-Reply-To: <b51cdb8a-d521-206c-3ac6-4ecbf7621caf@intel.com>
On 5/27/2022 11:55 AM, Matthew Auld wrote:
> On 27/05/2022 10:46, Das, Nirmoy wrote:
>>
>> On 5/26/2022 11:27 AM, Matthew Auld wrote:
>>> On 25/05/2022 10:59, Nirmoy Das wrote:
>>>> _i915_vma_move_to_active() can receive > 1 fences for
>>>> multiple batch buffers submission. Because dma_resv_add_fence()
>>>> can only accept one fence at a time, change _i915_vma_move_to_active()
>>>> to be aware of multiple fences so that it can add individual
>>>> fences to the dma resv object.
>>>>
>>>> v6: fix multi-line comment.
>>>> v5: remove double fence reservation for batch VMAs.
>>>> v4: Reserve fences for composite_fence on multi-batch contexts and
>>>> also reserve fence slots to composite_fence for each VMAs.
>>>> v3: dma_resv_reserve_fences is not cumulative so pass num_fences.
>>>> v2: make sure to reserve enough fence slots before adding.
>>>>
>>>> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/5614
>>>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>>>
>>> Do we need Fixes: ?
>>
>>
>> We can add:
>>
>> Fixes: 544460c33821 ("drm/i915: Multi-BB execbuf")
>
> Ok, so needs:
>
> Fixes: 544460c33821 ("drm/i915: Multi-BB execbuf")
> Cc: <stable@vger.kernel.org> # v5.16+
>
> Should I go ahead and push this to gt-next?
The patch will not get applied cleanly on 5.16 and 5.17. How do we
handle that generally ?
Thanks,
Nirmoy
>
>>
>>
>> Regards,
>>
>> Nirmoy
>>
>>
>>>
>>>> ---
>>>> .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 3 +-
>>>> drivers/gpu/drm/i915/i915_vma.c | 48
>>>> +++++++++++--------
>>>> 2 files changed, 30 insertions(+), 21 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
>>>> b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
>>>> index b279588c0672..8880d38d36b6 100644
>>>> --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
>>>> +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
>>>> @@ -1010,7 +1010,8 @@ static int eb_validate_vmas(struct
>>>> i915_execbuffer *eb)
>>>> }
>>>> }
>>>> - err = dma_resv_reserve_fences(vma->obj->base.resv, 1);
>>>> + /* Reserve enough slots to accommodate composite fences */
>>>> + err = dma_resv_reserve_fences(vma->obj->base.resv,
>>>> eb->num_batches);
>>>> if (err)
>>>> return err;
>>>> diff --git a/drivers/gpu/drm/i915/i915_vma.c
>>>> b/drivers/gpu/drm/i915/i915_vma.c
>>>> index 4f6db539571a..0bffb70b3c5f 100644
>>>> --- a/drivers/gpu/drm/i915/i915_vma.c
>>>> +++ b/drivers/gpu/drm/i915/i915_vma.c
>>>> @@ -23,6 +23,7 @@
>>>> */
>>>> #include <linux/sched/mm.h>
>>>> +#include <linux/dma-fence-array.h>
>>>> #include <drm/drm_gem.h>
>>>> #include "display/intel_frontbuffer.h"
>>>> @@ -1823,6 +1824,21 @@ int _i915_vma_move_to_active(struct i915_vma
>>>> *vma,
>>>> if (unlikely(err))
>>>> return err;
>>>> + /*
>>>> + * Reserve fences slot early to prevent an allocation after
>>>> preparing
>>>> + * the workload and associating fences with dma_resv.
>>>> + */
>>>> + if (fence && !(flags & __EXEC_OBJECT_NO_RESERVE)) {
>>>> + struct dma_fence *curr;
>>>> + int idx;
>>>> +
>>>> + dma_fence_array_for_each(curr, idx, fence)
>>>> + ;
>>>> + err = dma_resv_reserve_fences(vma->obj->base.resv, idx);
>>>> + if (unlikely(err))
>>>> + return err;
>>>> + }
>>>> +
>>>> if (flags & EXEC_OBJECT_WRITE) {
>>>> struct intel_frontbuffer *front;
>>>> @@ -1832,31 +1848,23 @@ int _i915_vma_move_to_active(struct
>>>> i915_vma *vma,
>>>> i915_active_add_request(&front->write, rq);
>>>> intel_frontbuffer_put(front);
>>>> }
>>>> + }
>>>> - if (!(flags & __EXEC_OBJECT_NO_RESERVE)) {
>>>> - err = dma_resv_reserve_fences(vma->obj->base.resv, 1);
>>>> - if (unlikely(err))
>>>> - return err;
>>>> - }
>>>> + if (fence) {
>>>> + struct dma_fence *curr;
>>>> + enum dma_resv_usage usage;
>>>> + int idx;
>>>> - if (fence) {
>>>> - dma_resv_add_fence(vma->obj->base.resv, fence,
>>>> - DMA_RESV_USAGE_WRITE);
>>>> + obj->read_domains = 0;
>>>> + if (flags & EXEC_OBJECT_WRITE) {
>>>> + usage = DMA_RESV_USAGE_WRITE;
>>>> obj->write_domain = I915_GEM_DOMAIN_RENDER;
>>>> - obj->read_domains = 0;
>>>> - }
>>>> - } else {
>>>> - if (!(flags & __EXEC_OBJECT_NO_RESERVE)) {
>>>> - err = dma_resv_reserve_fences(vma->obj->base.resv, 1);
>>>> - if (unlikely(err))
>>>> - return err;
>>>> + } else {
>>>> + usage = DMA_RESV_USAGE_READ;
>>>> }
>>>> - if (fence) {
>>>> - dma_resv_add_fence(vma->obj->base.resv, fence,
>>>> - DMA_RESV_USAGE_READ);
>>>> - obj->write_domain = 0;
>>>> - }
>>>> + dma_fence_array_for_each(curr, idx, fence)
>>>> + dma_resv_add_fence(vma->obj->base.resv, curr, usage);
>>>> }
>>>> if (flags & EXEC_OBJECT_NEEDS_FENCE && vma->fence)
next prev parent reply other threads:[~2022-05-27 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 9:59 [Intel-gfx] [PATCH v6] drm/i915: Individualize fences before adding to dma_resv obj Nirmoy Das
2022-05-25 13:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Individualize fences before adding to dma_resv obj (rev5) Patchwork
2022-05-25 20:16 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-26 9:27 ` [Intel-gfx] [PATCH v6] drm/i915: Individualize fences before adding to dma_resv obj Matthew Auld
2022-05-27 9:46 ` Das, Nirmoy
2022-05-27 9:55 ` Matthew Auld
2022-05-27 10:24 ` Das, Nirmoy [this message]
2022-05-27 11:37 ` Matthew Auld
2022-05-27 11:44 ` Das, Nirmoy
2022-05-26 10:00 ` Andrzej Hajda
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=4c0e1483-607c-5f0c-6085-1d94fcf60736@intel.com \
--to=nirmoy.das@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@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