From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967771AbcA0U0U (ORCPT ); Wed, 27 Jan 2016 15:26:20 -0500 Received: from mail-yk0-f174.google.com ([209.85.160.174]:35814 "EHLO mail-yk0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967714AbcA0UZp (ORCPT ); Wed, 27 Jan 2016 15:25:45 -0500 Date: Wed, 27 Jan 2016 18:25:40 -0200 From: Gustavo Padovan To: Emil Velikov Cc: Maarten Lankhorst , Greg Kroah-Hartman , "Linux-Kernel@Vger. Kernel. Org" , devel@driverdev.osuosl.org, ML dri-devel , Daniel Stone , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Riley Andrews , Daniel Vetter , Rob Clark , Greg Hackmann , John Harrison , Gustavo Padovan Subject: Re: [PATCH v2 01/11] dma-buf/sync_file: de-stage sync_file Message-ID: <20160127202540.GD3773@joana> Mail-Followup-To: Gustavo Padovan , Emil Velikov , Maarten Lankhorst , Greg Kroah-Hartman , "Linux-Kernel@Vger. Kernel. Org" , devel@driverdev.osuosl.org, ML dri-devel , Daniel Stone , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Riley Andrews , Daniel Vetter , Rob Clark , Greg Hackmann , John Harrison , Gustavo Padovan References: <1453901439-19467-1-git-send-email-gustavo@padovan.org> <1453901439-19467-2-git-send-email-gustavo@padovan.org> <56A8D4A7.1070409@linux.intel.com> <20160127170313.GC3773@joana> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Emil, 2016-01-27 Emil Velikov : > Hi Gustavo, > > On 27 January 2016 at 17:03, Gustavo Padovan wrote: > > Hi Maarten, > > > > 2016-01-27 Maarten Lankhorst : > > > >> Hey, > >> > >> Op 27-01-16 om 14:30 schreef Gustavo Padovan: > >> > From: Gustavo Padovan > >> > > >> > sync_file is useful to connect one or more fences to the file. The file is > >> > used by userspace to track fences. > >> > > >> > Signed-off-by: Gustavo Padovan > >> > > >> Is there a value in keeping the abi unchanged? > >> If not, then Documentation/ioctl/botching-up-ioctls.txt is worth a read. > > > > None from me. I'll look where we can improve the ABI. > > > Speaking of ABI... there are a couple of things that rang bells here: > - In most/all of the kernel a len/size named member variable > indicates the length of the extra data (zero sized array). While here > it includes the size of the struct as well. len in this case is the size of the buffer sent to the kernel, the total length (including the whole struct) is returned in the ioctl. > - struct sync_file_info_data::fence_info is of type __u8 yet it is "a > fence_info struct for every fence in the sync_file". Thus shouldn't > one use "struct fence_info" as the type ? Agreed. But I'm currently thinking if we really should keep this ioctl. Gustavo