Am Dienstag, den 27.11.2012, 13:31 +0200 schrieb Terje Bergström: > On 27.11.2012 12:37, Thierry Reding wrote: > > But in that case it should be made mandatory at first until proper IOMMU > > support is enabled on Tegra30. Then it can be checked at driver probe > > time whether or not to enable the extra checks. That way we don't need a > > special Kconfig option and we still get all the security that we need, > > right? > > I guess it depends on the level of security. > > If we want to only protect kernel and user space memory, this would be > sufficient and no firewall is needed if IOMMU is turned on. > > If we want to protect 2D buffers from each other, this is not sufficient. > I guess we could change IOMMU address spaces for the graphics units depending on the active channel. This would still be a bit of a performance hit, because of the necessary TLB flushing and so on, but should be much better than checking the whole command stream. This way you at least get security on a process level, as no process is able to corrupt another processes graphics resources. This is the same level of security as provided by the nouveau driver. But to do so all memory management has to be done in kernel and from the current submissions of the 2D infrastructure I fear that the current architecture does too much of that in userspace, but I'll hold back with any judgement until we actually get to see the userspace parts. Also to implement this strategy you have to take ownership of the graphics address space on a much lower level than the DMA API. This might take some work together with the IOMMU guys. Regards, Lucas _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
