From: "Das, Nirmoy" <nirmoy.das@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Accomodate for nested dma_resv fence addition
Date: Mon, 19 Dec 2022 13:52:53 +0200 [thread overview]
Message-ID: <3dfbc5b9-39d2-3c7b-cfb3-9d86645e9e31@intel.com> (raw)
In-Reply-To: <20221219113649.21926-1-nirmoy.das@intel.com>
This needs better explanation and probably CC to stable.
Please ignore this, I will resend.
Nirmoy
On 12/19/2022 1:36 PM, Nirmoy Das wrote:
> We have below nested fence slot reservation and then fence addition
> to that dma_resv.
> 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()
>
> A nested dma_resv_reserve_fences will not reserve extra slots and if the
> BO comes with lots of fences in its dma_resv, we might see:
>
> BUG_ON(fobj->num_fences >= fobj->max_fences);
>
> Suggested-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> 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;
>
next prev parent reply other threads:[~2022-12-19 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 11:36 [Intel-gfx] [PATCH] drm/i915: Accomodate for nested dma_resv fence addition Nirmoy Das
2022-12-19 11:52 ` Das, Nirmoy [this message]
2022-12-19 17:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " 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=3dfbc5b9-39d2-3c7b-cfb3-9d86645e9e31@intel.com \
--to=nirmoy.das@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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