From: Daniel Vetter <daniel@ffwll.ch>
To: "Christian König" <deathsimple@vodafone.de>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
daniel@ffwll.ch, gustavo@padovan.org, chris@chris-wilson.co.uk
Subject: Re: [PATCH 3/3] dma-buf/fence: add signal_on_any to the fence array
Date: Mon, 23 May 2016 15:50:50 +0200 [thread overview]
Message-ID: <20160523135049.GA27098@phenom.ffwll.local> (raw)
In-Reply-To: <1464002722-4989-3-git-send-email-deathsimple@vodafone.de>
On Mon, May 23, 2016 at 01:25:22PM +0200, Christian König wrote:
> From: Christian König <christian.koenig@amd.com>
>
> If @signal_on_any is true the fence array signals if any fence in the array
> signals, otherwise it signals when all fences in the array signal.
What do you need this for? Sounds neat, but I can't come up with a use
case. And that use case imo should be both in the commit message and
kerneldoc.
-Daniel
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/dma-buf/fence-array.c | 23 ++++++++++++++++-------
> include/linux/fence-array.h | 3 ++-
> 2 files changed, 18 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/dma-buf/fence-array.c b/drivers/dma-buf/fence-array.c
> index bbcf79f..726e840 100644
> --- a/drivers/dma-buf/fence-array.c
> +++ b/drivers/dma-buf/fence-array.c
> @@ -41,6 +41,7 @@ static void fence_array_cb_func(struct fence *f, struct fence_cb *cb)
>
> if (atomic_dec_and_test(&array->num_pending))
> fence_signal(&array->base);
> + fence_put(&array->base);
> }
>
> static bool fence_array_enable_signaling(struct fence *fence)
> @@ -51,10 +52,13 @@ static bool fence_array_enable_signaling(struct fence *fence)
>
> for (i = 0; i < array->num_fences; ++i) {
> cb[i].array = array;
> + fence_get(&array->base);
> if (!fence_add_callback(array->fences[i], &cb[i].cb,
> - fence_array_cb_func))
> + fence_array_cb_func)) {
> + fence_put(&array->base);
> if (atomic_dec_and_test(&array->num_pending))
> return false;
> + }
> }
>
> return true;
> @@ -90,10 +94,11 @@ const struct fence_ops fence_array_ops = {
>
> /**
> * fence_array_create - Create a custom fence array
> - * @num_fences: [in] number of fences to add in the array
> - * @fences: [in] array containing the fences
> - * @context: [in] fence context to use
> - * @seqno: [in] sequence number to use
> + * @num_fences: [in] number of fences to add in the array
> + * @fences: [in] array containing the fences
> + * @context: [in] fence context to use
> + * @seqno: [in] sequence number to use
> + * @signal_on_any [in] signal on any fence in the array
> *
> * Allocate a fence_array object and initialize the base fence with fence_init().
> * In case of error it returns NULL.
> @@ -101,9 +106,13 @@ const struct fence_ops fence_array_ops = {
> * The caller should allocte the fences array with num_fences size
> * and fill it with the fences it wants to add to the object. Ownership of this
> * array is take and fence_put() is used on each fence on release.
> + *
> + * If @signal_on_any is true the fence array signals if any fence in the array
> + * signals, otherwise it signals when all fences in the array signal.
> */
> struct fence_array *fence_array_create(int num_fences, struct fence **fences,
> - u64 context, unsigned seqno)
> + u64 context, unsigned seqno,
> + bool signal_on_any)
> {
> struct fence_array *array;
> size_t size = sizeof(*array);
> @@ -119,7 +128,7 @@ struct fence_array *fence_array_create(int num_fences, struct fence **fences,
> context, seqno);
>
> array->num_fences = num_fences;
> - atomic_set(&array->num_pending, num_fences);
> + atomic_set(&array->num_pending, signal_on_any ? 1 : num_fences);
> array->fences = fences;
>
> return array;
> diff --git a/include/linux/fence-array.h b/include/linux/fence-array.h
> index 593ab98..86baaa4 100644
> --- a/include/linux/fence-array.h
> +++ b/include/linux/fence-array.h
> @@ -67,6 +67,7 @@ static inline struct fence_array *to_fence_array(struct fence *fence)
> }
>
> struct fence_array *fence_array_create(int num_fences, struct fence **fences,
> - u64 context, unsigned seqno);
> + u64 context, unsigned seqno,
> + bool signal_on_any);
>
> #endif /* __LINUX_FENCE_ARRAY_H */
> --
> 2.5.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2016-05-23 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 11:25 [PATCH 1/3] dma-buf/fence: make fence context 64 bit v2 Christian König
2016-05-23 11:25 ` [PATCH 2/3] dma-buf/fence: add fence_array fences v5 Christian König
2016-05-23 13:53 ` Daniel Vetter
2016-05-23 11:25 ` [PATCH 3/3] dma-buf/fence: add signal_on_any to the fence array Christian König
2016-05-23 11:49 ` Chris Wilson
2016-05-23 13:50 ` Daniel Vetter [this message]
2016-05-23 13:58 ` Christian König
2016-05-23 14:05 ` Daniel Vetter
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=20160523135049.GA27098@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®