From: Chris Wilson <chris@chris-wilson.co.uk>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: dri-devel@lists.freedesktop.org, 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: [PATCH v2 3/4] dma-buf/sync_file: add sync_file_get_fence()
Date: Fri, 1 Jul 2016 14:21:33 +0100 [thread overview]
Message-ID: <20160701132133.GE1306@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1467378307-28088-4-git-send-email-gustavo@padovan.org>
On Fri, Jul 01, 2016 at 10:05:06AM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> Creates a function that given an sync file descriptor returns a
> fence containing all fences in the sync_file.
>
> v2: Comments by Daniel Vetter
> - Adapt to new version of fence_collection_init()
> - Hold a reference for the fence we return
>
> v3:
> - Adapt to use fput() directly
> - rename to sync_file_get_fence() as we always return one fence
>
> v4: Adapt to use fence_array
>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> ---
> drivers/dma-buf/sync_file.c | 24 ++++++++++++++++++++++++
> include/linux/sync_file.h | 1 +
> 2 files changed, 25 insertions(+)
>
> diff --git a/drivers/dma-buf/sync_file.c b/drivers/dma-buf/sync_file.c
> index 12dbf17..3ffaea8 100644
> --- a/drivers/dma-buf/sync_file.c
> +++ b/drivers/dma-buf/sync_file.c
> @@ -116,6 +116,30 @@ err:
> return NULL;
> }
>
> +/**
> + * sync_file_get_fence - get the fence related to the sync_file fd
> + * @fd: sync_file fd to get the fence from
> + *
> + * Ensures @fd references a valid sync_file and returns a fence that
> + * represents all fence in the sync_file. On error NULL is returned.
> + */
> +struct fence *sync_file_get_fence(int fd)
> +{
> + struct sync_file *sync_file;
> + struct fence *fence;
> +
> + sync_file = sync_file_fdget(fd);
> + if (!sync_file)
> + return NULL;
> +
> + fence = sync_file->fence;
> + fence_get(fence);
Or just fence = get_fence(sync_file->fence);
> + fput(sync_file->file);
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Using fence-array for this works very nicely, as we can then inspect the
fences returned and handle native fences for fd passed around.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2016-07-01 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 13:05 [PATCH v2 0/4] dma-buf/sync_file: rework fences on struct sync_file Gustavo Padovan
2016-07-01 13:05 ` [PATCH v2 1/4] dma-buf/fence-array: add fence_is_array() Gustavo Padovan
2016-07-01 13:05 ` [PATCH v2 2/4] dma-buf/sync_file: rework fence storage in struct file Gustavo Padovan
2016-07-01 13:19 ` Chris Wilson
2016-07-01 13:05 ` [PATCH v2 3/4] dma-buf/sync_file: add sync_file_get_fence() Gustavo Padovan
2016-07-01 13:21 ` Chris Wilson [this message]
2016-07-01 13:05 ` [PATCH v2 4/4] Documentation: add doc for sync_file_get_fence() 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=20160701132133.GE1306@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--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
all inboxes | Powered by JetHome®