diff options
author | Robin Murphy <robin.murphy@arm.com> | 2015-11-04 16:23:52 +0300 |
---|---|---|
committer | Catalin Marinas <catalin.marinas@arm.com> | 2015-11-16 13:05:35 +0300 |
commit | bd1c6ff74ce0bbd8cda6eb7763fa0e2625dfcc8b (patch) | |
tree | c9077a8f5382b8c535779396e67d44ff30c0f3fb /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 8005c49d9aea74d382f474ce11afbbc7d7130bec (diff) | |
download | linux-bd1c6ff74ce0bbd8cda6eb7763fa0e2625dfcc8b.tar.xz |
arm64/dma-mapping: Fix sizes in __iommu_{alloc,free}_attrs
The iommu-dma layer does its own size-alignment for coherent DMA
allocations based on IOMMU page sizes, but we still need to consider
CPU page sizes for the cases where a non-cacheable CPU mapping is
created. Whilst everything on the alloc/map path seems to implicitly
align things enough to make it work, some functions used by the
corresponding unmap/free path do not, which leads to problems freeing
odd-sized allocations. Either way it's something we really should be
handling explicitly, so do that to make both paths suitably robust.
Reported-by: Yong Wu <yong.wu@mediatek.com>
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions