On Tue, Dec 20, 2011 at 10:41:45AM -0600, Rob Clark wrote: > On Tue, Dec 20, 2011 at 9:41 AM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > > On Monday 19 December 2011, Semwal, Sumit wrote: > >> I didn't see a consensus on whether dma_buf should enforce some form > >> of serialization within the API - so atleast for v1 of dma-buf, I > >> propose to 'not' impose a restriction, and we can tackle it (add new > >> ops or enforce as design?) whenever we see the first need of it - will > >> that be ok? [I am bending towards the thought that it is a problem to > >> solve at a bigger platform than dma_buf.] > > > > The problem is generally understood for streaming mappings with a > > single device using it: if you have a long-running mapping, you have > > to use dma_sync_*. This obviously falls apart if you have multiple > > devices and no serialization between the accesses. > > > > If you don't want serialization, that implies that we cannot have > > use the dma_sync_* API on the buffer, which in turn implies that > > we cannot have streaming mappings. I think that's ok, but then > > you have to bring back the mmap API on the buffer if you want to > > allow any driver to provide an mmap function for a shared buffer. > > I'm thinking for a first version, we can get enough mileage out of it by saying: > 1) only exporter can mmap to userspace > 2) only importers that do not need CPU access to buffer.. > > This way we can get dmabuf into the kernel, maybe even for 3.3. I > know there are a lot of interesting potential uses where this stripped > down version is good enough. It probably isn't the final version, > maybe more features are added over time to deal with importers that > need CPU access to buffer, sync object, etc. But we have to start > somewhere. I agree with Rob here - I think especially for the coherency discussion some actual users of dma_buf on a bunch of insane platforms (i915 qualifies here too, because we do some cacheline flushing behind everyones back) would massively help in clarifying things. It also sounds like that at least for proper userspace mmap support we'd need some dma api extensions on at least arm, and that might take a while ... Cheers, Daniel -- Daniel Vetter Mail: daniel@xxxxxxxx Mobile: +41 (0)79 365 57 48 _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
