On 28.11.2012 16:06, Lucas Stach wrote: > Why do even need/use dma-buf for this use case? This is all one DRM > device, even if we separate host1x and gr2d as implementation modules. I didn't want to implement dependency to drm gem objects in nvhost, but we have thought about doing that. dma-buf brings quite a lot of overhead, so implementing support for gem buffers would make the sequence a bit leaner. nvhost already has infra to support multiple memory managers. > So standard way of doing this is: > 1. create gem object for pushbuffer > 2. create fake mmap offset for gem obj > 3. map pushbuf using the fake offset on the drm device > 4. at submit time zap the mapping > > You need this logic anyway, as normally we don't rely on userspace to > sync gpu and cpu, but use the kernel to handle the concurrency issues. Taking a step back - 2D streams are actually very short, in the order of <100 bytes. Just copying them to kernel space would actually be faster than doing MMU operations. I think for Tegra20 and non-IOMMU case, we just need to copy the command stream to kernel buffer. In Tegra30 IOMMU case reference to user space buffers are fine, as tampering the streams doesn't have any ill effects. Terje _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
