dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Gustavo Padovan <gustavo@padovan.org>, dri-devel@lists.freedesktop.org
Cc: marcheu@google.com, Daniel Stone <daniels@collabora.com>,
	seanpaul@google.com, Daniel Vetter <daniel.vetter@ffwll.ch>,
	linux-kernel@vger.kernel.org, laurent.pinchart@ideasonboard.com,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
	John Harrison <John.C.Harrison@Intel.com>,
	m.chehab@samsung.com
Subject: Re: [RFC v2 2/3] dma-buf/fence-array: add fence_array_teardown()
Date: Tue, 28 Jun 2016 11:56:27 +0200	[thread overview]
Message-ID: <577249CB.6050707@amd.com> (raw)
In-Reply-To: <1467055762-25881-3-git-send-email-gustavo@padovan.org>

Am 27.06.2016 um 21:29 schrieb Gustavo Padovan:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> As the array of fence callbacks held by an active struct fence_array
> each has a reference to the struct fence_array, when the owner of the
> fence_array is freed it must dispose of the callback references before
> it can free the fence_array. This can not happen simply during
> fence_release() because of the extra references and so we need a new
> function to run before the final fence_put().

As I said previously as well, this is completely superfluous.

The fence array keeps a reference to itself as long as not all callbacks 
are signaled.

So you only need to unregister your callback from the array itself and 
drop your reference when you don't need it any more in the sync file.

Additional to that having a special cleanup function like this strongly 
contradicts the approach of having an implementation independent interface.

So this is a clear NAK from my side.

Regards,
Christian.

>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Christian König <christian.koenig@amd.com>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> ---
>   drivers/dma-buf/fence-array.c | 25 +++++++++++++++++++++++++
>   include/linux/fence-array.h   |  1 +
>   2 files changed, 26 insertions(+)
>
> diff --git a/drivers/dma-buf/fence-array.c b/drivers/dma-buf/fence-array.c
> index a8731c8..8891357 100644
> --- a/drivers/dma-buf/fence-array.c
> +++ b/drivers/dma-buf/fence-array.c
> @@ -142,3 +142,28 @@ struct fence_array *fence_array_create(int num_fences, struct fence **fences,
>   	return array;
>   }
>   EXPORT_SYMBOL(fence_array_create);
> +
> +/**
> + * fence_array_teardown - Teardown and clean up a fence array
> + * @array:	[in]	the fence array to teardown
> + *
> + * This function removes callbacks and extra references to the base fence on
> + * the fence_array for each unsignalled fence in the array. It should be called
> + * before calling fence_put() to remove the last reference on a fence_array,
> + * otherwise the fence won't be released due to extra references holded by the
> + * the fences that still have signalling enabled.
> + */
> +void fence_array_teardown(struct fence_array *array)
> +{
> +	struct fence_array_cb *cb = (void *)(&array[1]);
> +	int i;
> +
> +	for (i = 0; i < array->num_fences; i++) {
> +		if (fence_is_signaled(array->fences[i]))
> +		    continue;
> +
> +		fence_remove_callback(array->fences[i], &cb[i].cb);
> +		fence_put(&array->base);
> +	}
> +}
> +EXPORT_SYMBOL(fence_array_teardown);
> diff --git a/include/linux/fence-array.h b/include/linux/fence-array.h
> index d2e9f40..9f1b923 100644
> --- a/include/linux/fence-array.h
> +++ b/include/linux/fence-array.h
> @@ -79,5 +79,6 @@ 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,
>   				       bool signal_on_any);
> +void fence_array_teardown(struct fence_array *array);
>   
>   #endif /* __LINUX_FENCE_ARRAY_H */

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-06-28  9:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 19:29 [RFC v2 0/3] dma-buf/sync_file: rework fences on struct sync_file Gustavo Padovan
2016-06-27 19:29 ` [RFC v2 1/3] dma-buf/fence-array: add fence_is_array() Gustavo Padovan
2016-06-27 19:29 ` [RFC v2 2/3] dma-buf/fence-array: add fence_array_teardown() Gustavo Padovan
2016-06-28  9:56   ` Christian König [this message]
2016-06-28 14:17     ` Gustavo Padovan
2016-06-28 15:05       ` Christian König
2016-06-28 15:17         ` Gustavo Padovan
2016-06-27 19:29 ` [RFC v2 3/3] dma-buf/sync_file: rework fence storage in struct file Gustavo Padovan
2016-06-28  8:02   ` Chris Wilson
2016-06-28 14:25     ` Gustavo Padovan
2016-06-28 15:09       ` Chris Wilson
2016-06-28 15:27         ` Gustavo Padovan

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=577249CB.6050707@amd.com \
    --to=christian.koenig@amd.com \
    --cc=John.C.Harrison@Intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=gustavo@padovan.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=marcheu@google.com \
    --cc=seanpaul@google.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;
as well as URLs for NNTP newsgroup(s).