From: Daniel Vetter <daniel@ffwll.ch>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Daniel Stone <daniels@collabora.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Rob Clark <robdclark@gmail.com>,
Greg Hackmann <ghackmann@google.com>,
John Harrison <John.C.Harrison@Intel.com>,
laurent.pinchart@ideasonboard.com, seanpaul@google.com,
marcheu@google.com, m.chehab@samsung.com,
Sumit Semwal <sumit.semwal@linaro.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [RFC 3/5] dma-buf/fence: add .get_fences() ops
Date: Tue, 12 Jul 2016 12:52:18 +0200 [thread overview]
Message-ID: <20160712105218.GE23520@phenom.ffwll.local> (raw)
In-Reply-To: <1466695790-2833-4-git-send-email-gustavo@padovan.org>
On Thu, Jun 23, 2016 at 12:29:48PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> get_fences() should return a copy of all fences in the fence as some
> fence subclass (such as fence_array) can store more than one fence at
> time.
>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> ---
> drivers/dma-buf/fence.c | 14 ++++++++++++++
> include/linux/fence.h | 3 +++
> 2 files changed, 17 insertions(+)
>
> diff --git a/drivers/dma-buf/fence.c b/drivers/dma-buf/fence.c
> index 4e61afb..f4094fd 100644
> --- a/drivers/dma-buf/fence.c
> +++ b/drivers/dma-buf/fence.c
> @@ -185,6 +185,20 @@ void fence_release(struct kref *kref)
> }
> EXPORT_SYMBOL(fence_release);
>
kerneldoc missing.
-Daniel
> +struct fence **fence_get_fences(struct fence *fence)
> +{
> + if (fence->ops->get_fences) {
> + return fence->ops->get_fences(fence);
> + } else {
> + struct fence **fences = kmalloc(sizeof(**fences), GFP_KERNEL);
> + if (!fences)
> + return NULL;
> + fences[0] = fence;
> + return fences;
> + }
> +}
> +EXPORT_SYMBOL(fence_get_fences);
> +
> void fence_teardown(struct fence *fence)
> {
> if (fence->ops->teardown)
> diff --git a/include/linux/fence.h b/include/linux/fence.h
> index 1d3b671..a7a2fbc 100644
> --- a/include/linux/fence.h
> +++ b/include/linux/fence.h
> @@ -111,6 +111,7 @@ struct fence_cb {
> * struct fence_ops - operations implemented for fence
> * @get_driver_name: returns the driver name.
> * @get_timeline_name: return the name of the context this fence belongs to.
> + * @get_fences: return an array with a copy of all fences in the fence.
> * @enable_signaling: enable software signaling of fence.
> * @signaled: [optional] peek whether the fence is signaled, can be null.
> * @wait: custom wait implementation, or fence_default_wait.
> @@ -175,6 +176,7 @@ struct fence_cb {
> struct fence_ops {
> const char * (*get_driver_name)(struct fence *fence);
> const char * (*get_timeline_name)(struct fence *fence);
> + struct fence ** (*get_fences)(struct fence *fence);
> bool (*enable_signaling)(struct fence *fence);
> bool (*signaled)(struct fence *fence);
> signed long (*wait)(struct fence *fence, bool intr, signed long timeout);
> @@ -189,6 +191,7 @@ struct fence_ops {
> void fence_init(struct fence *fence, const struct fence_ops *ops,
> spinlock_t *lock, u64 context, unsigned seqno);
>
> +struct fence **fence_get_fences(struct fence *fence);
> void fence_release(struct kref *kref);
> void fence_teardown(struct fence *fence);
> void fence_free(struct fence *fence);
> --
> 2.5.5
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2016-07-12 10:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 15:29 [RFC 0/5] rework fences on struct sync_file Gustavo Padovan
2016-06-23 15:29 ` [RFC 1/5] dma-buf/fence: add .teardown() ops Gustavo Padovan
2016-06-23 20:48 ` Chris Wilson
2016-06-24 13:19 ` Gustavo Padovan
2016-07-12 10:51 ` Daniel Vetter
2016-06-23 15:29 ` [RFC 2/5] dma-buf/fence-array: add fence_array_teardown() Gustavo Padovan
2016-06-23 15:29 ` [RFC 3/5] dma-buf/fence: add .get_fences() ops Gustavo Padovan
2016-06-23 20:40 ` Chris Wilson
2016-07-12 10:52 ` Daniel Vetter [this message]
2016-06-23 15:29 ` [RFC 4/5] dma-buf/fence-array: add fence_array_get_fences() Gustavo Padovan
2016-06-23 20:35 ` Chris Wilson
2016-06-23 15:29 ` [RFC 5/5] dma-buf/sync_file: rework fence storage in struct file Gustavo Padovan
2016-06-23 21:27 ` Chris Wilson
2016-06-24 13:23 ` Gustavo Padovan
2016-06-24 9:27 ` [RFC 0/5] rework fences on struct sync_file Christian König
2016-06-24 13:17 ` Gustavo Padovan
2016-06-24 14:14 ` Christian König
2016-06-24 14:59 ` Gustavo Padovan
2016-06-24 15:09 ` Christian König
2016-06-24 15:19 ` 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=20160712105218.GE23520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=John.C.Harrison@Intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ghackmann@google.com \
--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=maarten.lankhorst@linux.intel.com \
--cc=marcheu@google.com \
--cc=robdclark@gmail.com \
--cc=seanpaul@google.com \
--cc=sumit.semwal@linaro.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