On 28.11.2012 15:33, Lucas Stach wrote: > So this is obviously wrong. Userspace has to allocate a pushbuffer from > the kernel just as every other buffer, then map it into it's own address > space to push in commands. At submit time of the pushbuf kernel has to > make sure that userspace is not able to access the memory any more, i.e. > kernel shoots down the vma or pagetable of the vma. To keep overhead low > and not do any blocking you can just keep some pushbufs around for one > channel and switch over the pagetable entries to the next free buffer, > just make sure that userspace is never able to tamper with a buffer as > long as the gpu isn't done with it. That's really not something dma-buf APIs are equipped to handle. We need something to ensure user space doesn't have the buffer mapped (either return error if has, or zap the mapping), something to ensure user space cannot mmap the buffer, and something to revert this all once we're done. We could add these as special ops to tegradrm dmabuf code for now, and assume that command streams are always allocated by tegradrm. Now we allow any dmabuf to be used as buffers for command streams. And, with IOMMU I don't think we would need any of this. I guess we need to press the gas pedal on figuring out how to enable that for tegradrm on Tegra30. We already allocate multiple buffers to be able to fill in the next buffer once we've send one to kernel, so that part is ok. We reuse only once we know that the operations contained are done. Terje _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
