* Re: dma-buf/sync_file: de-stage sync_file
[not found] <20160521053153.14B99661B7C@gitolite.kernel.org>
@ 2016-05-26 2:42 ` Dave Jones
2016-05-27 21:06 ` Gustavo Padovan
0 siblings, 1 reply; 2+ messages in thread
From: Dave Jones @ 2016-05-26 2:42 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Gustavo Padovan, Daniel Vetter, Greg Kroah-Hartman
On Sat, May 21, 2016 at 05:31:53AM +0000, Linux Kernel wrote:
> dma-buf/sync_file: de-stage sync_file
>
> sync_file is useful to connect one or more fences to the file. The file is
> used by userspace to track fences between drivers that share DMA bufs.
>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
...
> +config SYNC_FILE
> + bool "sync_file support for fences"
> + default n
> + select ANON_INODES
> + select DMA_SHARED_BUFFER
> + ---help---
> + This option enables the fence framework synchronization to export
> + sync_files to userspace that can represent one or more fences.
For such a generic sounding CONFIG_ item, this is one of the more obtuse descriptions
in a kconfig we've had in a while, and the commit message doesn't give any more
clues as to why anyone might want to enable this.
I'm guessing this is some graphics thing given that Daniel reviewed it.
>From skimming the other commits, it seems to be some Android thing ?
Are there depends missing perhaps that might make this more obvious ?
Could you elaborate in the help text why someone might want to enable this ?
As is, it's just a bunch of words with no context for anyone who isn't
close to whatever domain this came from.
Dave
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: dma-buf/sync_file: de-stage sync_file
2016-05-26 2:42 ` dma-buf/sync_file: de-stage sync_file Dave Jones
@ 2016-05-27 21:06 ` Gustavo Padovan
0 siblings, 0 replies; 2+ messages in thread
From: Gustavo Padovan @ 2016-05-27 21:06 UTC (permalink / raw)
To: Dave Jones, Linux Kernel Mailing List, Daniel Vetter, Greg Kroah-Hartman
2016-05-25 Dave Jones <davej@codemonkey.org.uk>:
> On Sat, May 21, 2016 at 05:31:53AM +0000, Linux Kernel wrote:
>
> > dma-buf/sync_file: de-stage sync_file
> >
> > sync_file is useful to connect one or more fences to the file. The file is
> > used by userspace to track fences between drivers that share DMA bufs.
> >
> > Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> ...
>
> > +config SYNC_FILE
> > + bool "sync_file support for fences"
> > + default n
> > + select ANON_INODES
> > + select DMA_SHARED_BUFFER
> > + ---help---
> > + This option enables the fence framework synchronization to export
> > + sync_files to userspace that can represent one or more fences.
>
> For such a generic sounding CONFIG_ item, this is one of the more obtuse descriptions
> in a kconfig we've had in a while, and the commit message doesn't give any more
> clues as to why anyone might want to enable this.
>
> I'm guessing this is some graphics thing given that Daniel reviewed it.
> From skimming the other commits, it seems to be some Android thing ?
> Are there depends missing perhaps that might make this more obvious ?
You are right, only a few people understand this in the way I wrote. I
definitelly reword this. It is android framework to help userspace with
explict synchronization. DRM will require this, but the patches for that
did not land yet.
Gustavo
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-05-27 21:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20160521053153.14B99661B7C@gitolite.kernel.org>
2016-05-26 2:42 ` dma-buf/sync_file: de-stage sync_file Dave Jones
2016-05-27 21:06 ` Gustavo Padovan
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).