Searched hist:"249 baa54790171438524ba97e8e0485dd6aa2762" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/arch/x86/kernel/ |
| H A D | amd_gart_64.c | diff 249baa54790171438524ba97e8e0485dd6aa2762 Tue Aug 06 07:01:38 CDT 2019 Christoph Hellwig <hch@lst.de> dma-mapping: provide a better default ->get_required_mask
Most dma_map_ops instances are IOMMUs that work perfectly fine in 32-bits
of IOVA space, and the generic direct mapping code already provides its
own routines that is intelligent based on the amount of memory actually
present. Wire up the dma-direct routine for the ARM direct mapping code
as well, and otherwise default to the constant 32-bit mask. This way
we only need to override it for the occasional odd IOMMU that requires
64-bit IOVA support, or IOMMU drivers that are more efficient if they
can fall back to the direct mapping.
Signed-off-by: Christoph Hellwig <hch@lst.de>
|
| /openbmc/linux/kernel/dma/ |
| H A D | mapping.c | diff 249baa54790171438524ba97e8e0485dd6aa2762 Tue Aug 06 07:01:38 CDT 2019 Christoph Hellwig <hch@lst.de> dma-mapping: provide a better default ->get_required_mask
Most dma_map_ops instances are IOMMUs that work perfectly fine in 32-bits
of IOVA space, and the generic direct mapping code already provides its
own routines that is intelligent based on the amount of memory actually
present. Wire up the dma-direct routine for the ARM direct mapping code
as well, and otherwise default to the constant 32-bit mask. This way
we only need to override it for the occasional odd IOMMU that requires
64-bit IOVA support, or IOMMU drivers that are more efficient if they
can fall back to the direct mapping.
Signed-off-by: Christoph Hellwig <hch@lst.de>
|
| /openbmc/linux/arch/powerpc/platforms/ps3/ |
| H A D | system-bus.c | diff 249baa54790171438524ba97e8e0485dd6aa2762 Tue Aug 06 07:01:38 CDT 2019 Christoph Hellwig <hch@lst.de> dma-mapping: provide a better default ->get_required_mask
Most dma_map_ops instances are IOMMUs that work perfectly fine in 32-bits
of IOVA space, and the generic direct mapping code already provides its
own routines that is intelligent based on the amount of memory actually
present. Wire up the dma-direct routine for the ARM direct mapping code
as well, and otherwise default to the constant 32-bit mask. This way
we only need to override it for the occasional odd IOMMU that requires
64-bit IOVA support, or IOMMU drivers that are more efficient if they
can fall back to the direct mapping.
Signed-off-by: Christoph Hellwig <hch@lst.de>
|
| /openbmc/linux/arch/arm/mm/ |
| H A D | dma-mapping.c | diff 249baa54790171438524ba97e8e0485dd6aa2762 Tue Aug 06 07:01:38 CDT 2019 Christoph Hellwig <hch@lst.de> dma-mapping: provide a better default ->get_required_mask
Most dma_map_ops instances are IOMMUs that work perfectly fine in 32-bits
of IOVA space, and the generic direct mapping code already provides its
own routines that is intelligent based on the amount of memory actually
present. Wire up the dma-direct routine for the ARM direct mapping code
as well, and otherwise default to the constant 32-bit mask. This way
we only need to override it for the occasional odd IOMMU that requires
64-bit IOVA support, or IOMMU drivers that are more efficient if they
can fall back to the direct mapping.
Signed-off-by: Christoph Hellwig <hch@lst.de>
|