From: Andi Shyti <andi.shyti@linux.intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: paulo.r.zanoni@intel.com, jani.nikula@intel.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
thomas.hellstrom@intel.com, matthew.auld@intel.com,
daniel.vetter@intel.com, christian.koenig@amd.com
Subject: Re: [Intel-gfx] [PATCH v7 20/20] drm/i915/vm_bind: Async vm_unbind support
Date: Tue, 15 Nov 2022 16:58:42 +0100 [thread overview]
Message-ID: <Y3O3Murna92s7iKL@ashyti-mobl2.lan> (raw)
In-Reply-To: <20221113075732.32100-21-niranjana.vishwanathapura@intel.com>
Hi Niranjana,
On Sat, Nov 12, 2022 at 11:57:32PM -0800, Niranjana Vishwanathapura wrote:
> Asynchronously unbind the vma upon vm_unbind call.
> Fall back to synchronous unbind if backend doesn't support
> async unbind or if async unbind fails.
>
> No need for vm_unbind out fence support as i915 will internally
> handle all sequencing and user need not try to sequence any
> operation with the unbind completion.
>
> v2: use i915_vma_destroy_async in vm_unbind ioctl
>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
> .../drm/i915/gem/i915_gem_vm_bind_object.c | 2 +-
> drivers/gpu/drm/i915/i915_vma.c | 51 +++++++++++++++++--
> drivers/gpu/drm/i915/i915_vma.h | 1 +
> include/uapi/drm/i915_drm.h | 3 +-
> 4 files changed, 51 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_vm_bind_object.c b/drivers/gpu/drm/i915/gem/i915_gem_vm_bind_object.c
> index d87d1210365b..36651b447966 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_vm_bind_object.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_vm_bind_object.c
> @@ -210,7 +210,7 @@ static int i915_gem_vm_unbind_vma(struct i915_address_space *vm,
> */
> obj = vma->obj;
> i915_gem_object_lock(obj, NULL);
> - i915_vma_destroy(vma);
> + i915_vma_destroy_async(vma);
> i915_gem_object_unlock(obj);
>
> i915_gem_object_put(obj);
> diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
> index 7cf77c67d755..483d25f2425c 100644
> --- a/drivers/gpu/drm/i915/i915_vma.c
> +++ b/drivers/gpu/drm/i915/i915_vma.c
> @@ -42,6 +42,8 @@
> #include "i915_vma.h"
> #include "i915_vma_resource.h"
>
> +static struct dma_fence *__i915_vma_unbind_async(struct i915_vma *vma);
> +
> static inline void assert_vma_held_evict(const struct i915_vma *vma)
> {
> /*
> @@ -1713,7 +1715,7 @@ void i915_vma_reopen(struct i915_vma *vma)
> spin_unlock_irq(>->closed_lock);
> }
>
> -static void force_unbind(struct i915_vma *vma)
> +static void force_unbind(struct i915_vma *vma, bool async)
I still like the defines on this, they look cleaner, but it's a
matter of taste.
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
next prev parent reply other threads:[~2022-11-15 15:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 7:57 [Intel-gfx] [PATCH v7 00/20] drm/i915/vm_bind: Add VM_BIND functionality Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 01/20] drm/i915/vm_bind: Expose vm lookup function Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 02/20] drm/i915/vm_bind: Add __i915_sw_fence_await_reservation() Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 03/20] drm/i915/vm_bind: Expose i915_gem_object_max_page_size() Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 04/20] drm/i915/vm_bind: Add support to create persistent vma Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 05/20] drm/i915/vm_bind: Implement bind and unbind of object Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 06/20] drm/i915/vm_bind: Support for VM private BOs Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 07/20] drm/i915/vm_bind: Add support to handle object evictions Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 08/20] drm/i915/vm_bind: Support persistent vma activeness tracking Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 09/20] drm/i915/vm_bind: Add out fence support Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 10/20] drm/i915/vm_bind: Abstract out common execbuf functions Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 11/20] drm/i915/vm_bind: Use common execbuf functions in execbuf path Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 12/20] drm/i915/vm_bind: Implement I915_GEM_EXECBUFFER3 ioctl Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 13/20] drm/i915/vm_bind: Update i915_vma_verify_bind_complete() Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 14/20] drm/i915/vm_bind: Expose i915_request_await_bind() Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 15/20] drm/i915/vm_bind: Handle persistent vmas in execbuf3 Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 16/20] drm/i915/vm_bind: userptr dma-resv changes Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 17/20] drm/i915/vm_bind: Limit vm_bind mode to non-recoverable contexts Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 18/20] drm/i915/vm_bind: Add uapi for user to enable vm_bind_mode Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 19/20] drm/i915/vm_bind: Render VM_BIND documentation Niranjana Vishwanathapura
2022-11-13 7:57 ` [Intel-gfx] [PATCH v7 20/20] drm/i915/vm_bind: Async vm_unbind support Niranjana Vishwanathapura
2022-11-15 11:05 ` Matthew Auld
2022-11-15 16:15 ` Niranjana Vishwanathapura
2022-11-15 16:20 ` Matthew Auld
2022-11-15 16:33 ` Niranjana Vishwanathapura
2022-11-15 23:15 ` Niranjana Vishwanathapura
2022-11-16 0:37 ` Niranjana Vishwanathapura
2022-11-23 11:42 ` Matthew Auld
2022-11-29 23:26 ` Niranjana Vishwanathapura
2022-12-01 10:10 ` Matthew Auld
2022-12-01 15:11 ` Niranjana Vishwanathapura
2022-11-15 15:58 ` Andi Shyti [this message]
2022-11-15 16:20 ` Niranjana Vishwanathapura
2022-11-13 8:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/vm_bind: Add VM_BIND functionality (rev10) Patchwork
2022-11-13 8:39 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-11-13 9:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-13 11:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-11-18 23:53 ` [Intel-gfx] [PATCH v7 00/20] drm/i915/vm_bind: Add VM_BIND functionality Zanoni, Paulo R
2022-11-30 3:53 ` Niranjana Vishwanathapura
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=Y3O3Murna92s7iKL@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=matthew.auld@intel.com \
--cc=niranjana.vishwanathapura@intel.com \
--cc=paulo.r.zanoni@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