diff options
| author | Robin Murphy <robin.murphy@arm.com> | 2017-10-13 19:23:39 +0100 |
|---|---|---|
| committer | Alex Williamson <alex.williamson@redhat.com> | 2017-11-06 10:27:06 -0700 |
| commit | 1c7e7c0278df968221a5edb1a293423e13b13814 (patch) | |
| tree | f17e2a6ec535867d06bd76321d76deb4159c4e9a /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 105a004e2187609a74f75d55fd0f9a054b49d60a (diff) | |
iommu/ipmmu-vmsa: Unify domain alloc/free
We have two implementations for ipmmu_ops->alloc depending on
CONFIG_IOMMU_DMA, the difference being whether they accept the
IOMMU_DOMAIN_DMA type or not. However, iommu_dma_get_cookie() is
guaranteed to return an error when !CONFIG_IOMMU_DMA, so if
ipmmu_domain_alloc_dma() was actually checking and handling the return
value correctly, it would behave the same as ipmmu_domain_alloc()
anyway.
Similarly for freeing; iommu_put_dma_cookie() is robust by design.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions