[PATCH v6 1/3] iommu: Implement common IOMMU ops for DMA mapping
Russell King - ARM Linux
linux at arm.linux.org.uk
Wed Nov 4 02:50:57 PST 2015
On Wed, Nov 04, 2015 at 06:48:50PM +0900, Tomasz Figa wrote:
> There is no requirement, but shouldn't it be desired for the mapping
> code to map them as such? Otherwise, how could the IOMMU use case you
> described above (address translator for devices which don't have the
> capability to address a scatterlist) be handled properly?
It's up to the IOMMU code to respect the parameters that the device has
supplied to it via the device_dma_parameters. This doesn't currently
allow a device to say "I want this scatterlist to be mapped as a
contiguous device address", so really if a device has such a requirement,
at the moment the device driver _must_ check the dma_map_sg() return
value and act accordingly.
While it's possible to say "an IOMMU should map as a single contiguous
address" what happens when the IOMMU's device address space becomes
> Is the general conclusion now that dma_map_sg() should not be used to
> create IOMMU mappings and we should make a step backwards making all
> drivers (or frameworks, such as videobuf2) do that manually? That
> would be really backwards, because code not aware of IOMMU existence
> at all would have to become aware of it.
No. The DMA API has always had the responsibility for managing the
IOMMU device, which may well be shared between multiple different
However, if the IOMMU is part of a device IP block (such as a GPU)
then the decision on whether the DMA API should be used or not is up
to the driver author. If it has special management requirements,
then it's probably appropriate for the device driver to manage it by
For example, a GPUs MMU may need something inserted into the GPUs
command stream to flush the MMU TLBs. Such cases are inappropriate
to be using the DMA API for IOMMU management.
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
More information about the linux-arm-kernel