From: "Das, Nirmoy" <nirmoy.das@intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, jianshui.yu@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Reserve enough fence slot for i915_vma_unbind_async
Date: Thu, 5 Jan 2023 11:03:48 +0100 [thread overview]
Message-ID: <16130c3b-b208-be46-37e3-2c387a4a2d5e@intel.com> (raw)
In-Reply-To: <CAM0jSHNCOE7_KNpc=iTqPf4WOrA_YZ+TzhpVaMQ1hFxqgHB_0Q@mail.gmail.com>
On 1/5/2023 10:56 AM, Matthew Auld wrote:
> On Fri, 23 Dec 2022 at 09:20, Nirmoy Das <nirmoy.das@intel.com> wrote:
>> A nested dma_resv_reserve_fences(1) will not reserve slot from the
>> 2nd call onwards and folowing dma_resv_add_fence() might hit the
>> "BUG_ON(fobj->num_fences >= fobj->max_fences)" check.
>>
>> I915 hit above nested dma_resv case in ttm_bo_handle_move_mem() with
>> async unbind:
>>
>> dma_resv_reserve_fences() from --> ttm_bo_handle_move_mem()
>> dma_resv_reserve_fences() from --> i915_vma_unbind_async()
>> dma_resv_add_fence() from --> i915_vma_unbind_async()
>> dma_resv_add_fence() from -->ttm_bo_move_accel_cleanup()
>>
>> Resolve this by adding an extra fence in i915_vma_unbind_async().
>>
>> Suggested-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
> Does this need a fixes tag?
>
> Fixes: 2f6b90da9192 ("drm/i915: Use vma resources for async unbinding")
> Cc: <stable@vger.kernel.org> # v5.18+
>
> I can add when pushing.
Yes, please add that.
Thanks,
Nirmoy
>
>> ---
>> drivers/gpu/drm/i915/i915_vma.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
>> index 7d044888ac33..5ac4c1c2403c 100644
>> --- a/drivers/gpu/drm/i915/i915_vma.c
>> +++ b/drivers/gpu/drm/i915/i915_vma.c
>> @@ -2149,7 +2149,7 @@ int i915_vma_unbind_async(struct i915_vma *vma, bool trylock_vm)
>> if (!obj->mm.rsgt)
>> return -EBUSY;
>>
>> - err = dma_resv_reserve_fences(obj->base.resv, 1);
>> + err = dma_resv_reserve_fences(obj->base.resv, 2);
>> if (err)
>> return -EBUSY;
>>
>> --
>> 2.38.0
>>
prev parent reply other threads:[~2023-01-05 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 9:20 [Intel-gfx] [PATCH] drm/i915: Reserve enough fence slot for i915_vma_unbind_async Nirmoy Das
2022-12-23 10:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-12-23 11:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-01-05 9:56 ` [Intel-gfx] [PATCH] " Matthew Auld
2023-01-05 10:03 ` Das, Nirmoy [this message]
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=16130c3b-b208-be46-37e3-2c387a4a2d5e@intel.com \
--to=nirmoy.das@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jianshui.yu@intel.com \
--cc=matthew.william.auld@gmail.com \
--cc=thomas.hellstrom@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