public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Hackmann <ghackmann@google.com>
To: Gustavo Padovan <gustavo@padovan.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	dri-devel@lists.freedesktop.org,
	"Daniel Stone" <daniels@collabora.com>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Riley Andrews" <riandrews@android.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Rob Clark" <robdclark@gmail.com>,
	"John Harrison" <John.C.Harrison@Intel.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH v7 1/5] staging/android: add num_fences field to struct sync_file_info
Date: Tue, 8 Mar 2016 18:36:31 -0800	[thread overview]
Message-ID: <56DF8C2F.1040904@google.com> (raw)
In-Reply-To: <1457034046-27678-1-git-send-email-gustavo@padovan.org>

On 03/03/2016 11:40 AM, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> Inform userspace how many fences are in the sync_fence_info field.
>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
>   drivers/staging/android/sync.c      | 2 ++
>   drivers/staging/android/uapi/sync.h | 2 ++
>   2 files changed, 4 insertions(+)
>
> diff --git a/drivers/staging/android/sync.c b/drivers/staging/android/sync.c
> index 3a8f210..31aa462 100644
> --- a/drivers/staging/android/sync.c
> +++ b/drivers/staging/android/sync.c
> @@ -525,6 +525,8 @@ static long sync_file_ioctl_fence_info(struct sync_file *sync_file,
>   	if (info->status >= 0)
>   		info->status = !info->status;
>
> +	info->num_fences = sync_file->num_fences;
> +
>   	len = sizeof(struct sync_file_info);
>
>   	for (i = 0; i < sync_file->num_fences; ++i) {
> diff --git a/drivers/staging/android/uapi/sync.h b/drivers/staging/android/uapi/sync.h
> index a0cf357..4ffb7cc 100644
> --- a/drivers/staging/android/uapi/sync.h
> +++ b/drivers/staging/android/uapi/sync.h
> @@ -47,12 +47,14 @@ struct sync_fence_info {
>    *		userspace including pt_info.
>    * @name:	name of fence
>    * @status:	status of fence. 1: signaled 0:active <0:error
> + * @num_fences	number of fences in the sync_file
>    * @sync_fence_info: array of sync_fence_info for every fence in the sync_file
>    */
>   struct sync_file_info {
>   	__u32	len;
>   	char	name[32];
>   	__s32	status;
> +	__u32	num_fences;
>
>   	__u8	sync_fence_info[0];
>   };
>

Greg, this is ultimately your call.  But to echo what I said before, I'm 
OK with the ABI break here if that's what's needed to get sync moved out 
of staging.

Pragmatically speaking, this won't break ordinary Android apps, because 
they don't get direct access to sync fence fds to begin with.  Some 
privileged system processes do, but they go through libsync, which can 
be changed to deal with the ABI differences.

Anyway, for the whole series:

Acked-by: Greg Hackmann <ghackmann@google.com>

  parent reply	other threads:[~2016-03-09  2:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 19:40 [PATCH v7 1/5] staging/android: add num_fences field to struct sync_file_info Gustavo Padovan
2016-03-03 19:40 ` [PATCH v7 2/5] staging/android: rename SYNC_IOC_FENCE_INFO Gustavo Padovan
2016-03-03 19:40 ` [PATCH v7 3/5] staging/android: remove redundant comments on sync_merge_data Gustavo Padovan
2016-03-03 19:40 ` [PATCH v7 4/5] staging/android: refactor SYNC_IOC_FILE_INFO Gustavo Padovan
2016-03-03 19:40 ` [PATCH v7 5/5] staging/android: add flags member to sync ioctl structs Gustavo Padovan
2016-03-03 22:42   ` [PATCH] staging/android: change IOCTLs opcode after ABI change Gustavo Padovan
2016-03-09  2:36     ` Greg Hackmann
2016-03-11 22:00     ` Greg Kroah-Hartman
2016-03-12 17:34       ` Rob Clark
2016-03-09  2:36 ` Greg Hackmann [this message]
2016-03-31  1:22 ` [PATCH v7 1/5] staging/android: add num_fences field to struct sync_file_info Greg Kroah-Hartman
2016-03-31  2:53   ` Gustavo Padovan
2016-03-31  3:02     ` Greg Kroah-Hartman

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=56DF8C2F.1040904@google.com \
    --to=ghackmann@google.com \
    --cc=John.C.Harrison@Intel.com \
    --cc=arve@android.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=gustavo@padovan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=riandrews@android.com \
    --cc=robdclark@gmail.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