From: Matthew Auld <matthew.auld@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: paulo.r.zanoni@intel.com, jani.nikula@intel.com,
thomas.hellstrom@intel.com, daniel.vetter@intel.com,
christian.koenig@amd.com
Subject: Re: [Intel-gfx] [PATCH v4 14/17] drm/i915/vm_bind: Expose i915_request_await_bind()
Date: Wed, 19 Oct 2022 17:09:32 +0100 [thread overview]
Message-ID: <5b8f3280-908d-df3d-e237-9de294326621@intel.com> (raw)
In-Reply-To: <20221018071630.3831-15-niranjana.vishwanathapura@intel.com>
On 18/10/2022 08:16, Niranjana Vishwanathapura wrote:
> Rename __i915_request_await_bind() as i915_request_await_bind()
> and make it non-static as it will be used in execbuf3 ioctl path.
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
> drivers/gpu/drm/i915/i915_vma.c | 8 +-------
> drivers/gpu/drm/i915/i915_vma.h | 6 ++++++
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
> index 4975fc662c86..ab89e907f2eb 100644
> --- a/drivers/gpu/drm/i915/i915_vma.c
> +++ b/drivers/gpu/drm/i915/i915_vma.c
> @@ -1884,18 +1884,12 @@ void i915_vma_revoke_mmap(struct i915_vma *vma)
> list_del(&vma->obj->userfault_link);
> }
>
> -static int
> -__i915_request_await_bind(struct i915_request *rq, struct i915_vma *vma)
> -{
> - return __i915_request_await_exclusive(rq, &vma->active);
> -}
> -
> static int __i915_vma_move_to_active(struct i915_vma *vma, struct i915_request *rq)
> {
> int err;
>
> /* Wait for the vma to be bound before we start! */
> - err = __i915_request_await_bind(rq, vma);
> + err = i915_request_await_bind(rq, vma);
> if (err)
> return err;
>
> diff --git a/drivers/gpu/drm/i915/i915_vma.h b/drivers/gpu/drm/i915/i915_vma.h
> index 04770f8ba815..19e57e12b956 100644
> --- a/drivers/gpu/drm/i915/i915_vma.h
> +++ b/drivers/gpu/drm/i915/i915_vma.h
> @@ -54,6 +54,12 @@ void i915_vma_unpin_and_release(struct i915_vma **p_vma, unsigned int flags);
> /* do not reserve memory to prevent deadlocks */
> #define __EXEC_OBJECT_NO_RESERVE BIT(31)
>
> +static inline int
> +i915_request_await_bind(struct i915_request *rq, struct i915_vma *vma)
Some kernel doc might be good?
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> +{
> + return __i915_request_await_exclusive(rq, &vma->active);
> +}
> +
> int __must_check _i915_vma_move_to_active(struct i915_vma *vma,
> struct i915_request *rq,
> struct dma_fence *fence,
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Auld <matthew.auld@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: matthew.brost@intel.com, paulo.r.zanoni@intel.com,
tvrtko.ursulin@intel.com, jani.nikula@intel.com,
lionel.g.landwerlin@intel.com, thomas.hellstrom@intel.com,
jason@jlekstrand.net, andi.shyti@linux.intel.com,
daniel.vetter@intel.com, christian.koenig@amd.com
Subject: Re: [PATCH v4 14/17] drm/i915/vm_bind: Expose i915_request_await_bind()
Date: Wed, 19 Oct 2022 17:09:32 +0100 [thread overview]
Message-ID: <5b8f3280-908d-df3d-e237-9de294326621@intel.com> (raw)
In-Reply-To: <20221018071630.3831-15-niranjana.vishwanathapura@intel.com>
On 18/10/2022 08:16, Niranjana Vishwanathapura wrote:
> Rename __i915_request_await_bind() as i915_request_await_bind()
> and make it non-static as it will be used in execbuf3 ioctl path.
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
> drivers/gpu/drm/i915/i915_vma.c | 8 +-------
> drivers/gpu/drm/i915/i915_vma.h | 6 ++++++
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
> index 4975fc662c86..ab89e907f2eb 100644
> --- a/drivers/gpu/drm/i915/i915_vma.c
> +++ b/drivers/gpu/drm/i915/i915_vma.c
> @@ -1884,18 +1884,12 @@ void i915_vma_revoke_mmap(struct i915_vma *vma)
> list_del(&vma->obj->userfault_link);
> }
>
> -static int
> -__i915_request_await_bind(struct i915_request *rq, struct i915_vma *vma)
> -{
> - return __i915_request_await_exclusive(rq, &vma->active);
> -}
> -
> static int __i915_vma_move_to_active(struct i915_vma *vma, struct i915_request *rq)
> {
> int err;
>
> /* Wait for the vma to be bound before we start! */
> - err = __i915_request_await_bind(rq, vma);
> + err = i915_request_await_bind(rq, vma);
> if (err)
> return err;
>
> diff --git a/drivers/gpu/drm/i915/i915_vma.h b/drivers/gpu/drm/i915/i915_vma.h
> index 04770f8ba815..19e57e12b956 100644
> --- a/drivers/gpu/drm/i915/i915_vma.h
> +++ b/drivers/gpu/drm/i915/i915_vma.h
> @@ -54,6 +54,12 @@ void i915_vma_unpin_and_release(struct i915_vma **p_vma, unsigned int flags);
> /* do not reserve memory to prevent deadlocks */
> #define __EXEC_OBJECT_NO_RESERVE BIT(31)
>
> +static inline int
> +i915_request_await_bind(struct i915_request *rq, struct i915_vma *vma)
Some kernel doc might be good?
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> +{
> + return __i915_request_await_exclusive(rq, &vma->active);
> +}
> +
> int __must_check _i915_vma_move_to_active(struct i915_vma *vma,
> struct i915_request *rq,
> struct dma_fence *fence,
next prev parent reply other threads:[~2022-10-19 16:15 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 7:16 [Intel-gfx] [PATCH v4 00/17] drm/i915/vm_bind: Add VM_BIND functionality Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 01/17] drm/i915/vm_bind: Expose vm lookup function Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 02/17] drm/i915/vm_bind: Add __i915_sw_fence_await_reservation() Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 03/17] drm/i915/vm_bind: Expose i915_gem_object_max_page_size() Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 04/17] drm/i915/vm_bind: Add support to create persistent vma Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 05/17] drm/i915/vm_bind: Implement bind and unbind of object Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 06/17] drm/i915/vm_bind: Support for VM private BOs Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 07/17] drm/i915/vm_bind: Add support to handle object evictions Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 08/17] drm/i915/vm_bind: Support persistent vma activeness tracking Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 09/17] drm/i915/vm_bind: Add out fence support Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 15:28 ` [Intel-gfx] " Matthew Auld
2022-10-18 15:28 ` Matthew Auld
2022-10-19 2:43 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-19 2:43 ` Niranjana Vishwanathapura
2022-10-19 14:24 ` [Intel-gfx] " Matthew Auld
2022-10-19 14:24 ` Matthew Auld
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 10/17] drm/i915/vm_bind: Abstract out common execbuf functions Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 11/17] drm/i915/vm_bind: Use common execbuf functions in execbuf path Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 12/17] drm/i915/vm_bind: Implement I915_GEM_EXECBUFFER3 ioctl Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 17:30 ` [Intel-gfx] " Matthew Auld
2022-10-18 17:30 ` Matthew Auld
2022-10-19 4:10 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-19 4:10 ` Niranjana Vishwanathapura
2022-10-19 15:20 ` [Intel-gfx] " Matthew Auld
2022-10-19 15:20 ` Matthew Auld
2022-10-19 19:03 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-19 19:03 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 13/17] drm/i915/vm_bind: Update i915_vma_verify_bind_complete() Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-19 16:07 ` [Intel-gfx] " Matthew Auld
2022-10-19 16:07 ` Matthew Auld
2022-10-19 18:28 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-19 18:28 ` Niranjana Vishwanathapura
2022-10-20 9:16 ` [Intel-gfx] " Matthew Auld
2022-10-20 9:16 ` Matthew Auld
2022-10-20 16:51 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-20 16:51 ` Niranjana Vishwanathapura
2022-10-20 17:06 ` [Intel-gfx] " Matthew Auld
2022-10-20 17:06 ` Matthew Auld
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 14/17] drm/i915/vm_bind: Expose i915_request_await_bind() Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-19 16:09 ` Matthew Auld [this message]
2022-10-19 16:09 ` Matthew Auld
2022-10-19 18:04 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-19 18:04 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 15/17] drm/i915/vm_bind: Handle persistent vmas in execbuf3 Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 18:01 ` [Intel-gfx] " Matthew Auld
2022-10-18 18:01 ` Matthew Auld
2022-10-18 20:20 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-18 20:20 ` Niranjana Vishwanathapura
2022-10-19 5:17 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-20 16:33 ` Matthew Auld
2022-10-20 16:33 ` Matthew Auld
2022-10-20 16:39 ` [Intel-gfx] " Matthew Auld
2022-10-20 16:39 ` Matthew Auld
2022-10-20 17:06 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-20 17:06 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 16/17] drm/i915/vm_bind: userptr dma-resv changes Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-20 14:27 ` [Intel-gfx] " Andi Shyti
2022-10-20 14:27 ` Andi Shyti
2022-10-20 19:05 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-20 19:05 ` Niranjana Vishwanathapura
2022-10-20 21:20 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-20 16:29 ` Matthew Auld
2022-10-20 16:29 ` Matthew Auld
2022-10-20 16:39 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-20 16:39 ` Niranjana Vishwanathapura
2022-10-18 7:16 ` [Intel-gfx] [PATCH v4 17/17] drm/i915/vm_bind: Add uapi for user to enable vm_bind_mode Niranjana Vishwanathapura
2022-10-18 7:16 ` Niranjana Vishwanathapura
2022-10-18 16:03 ` [Intel-gfx] " Matthew Auld
2022-10-18 16:03 ` Matthew Auld
2022-10-18 16:48 ` [Intel-gfx] " Niranjana Vishwanathapura
2022-10-18 16:48 ` Niranjana Vishwanathapura
2022-10-18 7:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/vm_bind: Add VM_BIND functionality (rev7) Patchwork
2022-10-18 7:55 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-18 8:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-19 1:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=5b8f3280-908d-df3d-e237-9de294326621@intel.com \
--to=matthew.auld@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.