| commit | 8aca92d82d9f259e0b6b0c81e5eb9baaf471e6ad | |
| author | Alexey Kardashevskiy <aik@ozlabs.ru> | |
| Fri, 5 Jun 2015 06:34:57 +0000 (5 16:34 +1000) | ||
| committer | Michael Ellerman <mpe@ellerman.id.au> | |
| Thu, 11 Jun 2015 05:14:55 +0000 (11 15:14 +1000) | ||
| tree | 2bbb9f59ef5e0a195bd983ecf64ec949fb7fd3f7 | treesnapshot (tar.gz zip) |
| parent | ac9a58891a965216e9cb549a0a2012b97e3abcce | commitdiff |
powerpc/iommu: Always release iommu_table in iommu_free_table()
At the moment iommu_free_table() only releases memory if
the table was initialized for the platform code use, i.e. it had
it_map initialized (which purpose is to track DMA memory space use).
With dynamic DMA windows, we will need to be able to release
iommu_table even if it was used for VFIO in which case it_map is NULL
so does the patch.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
At the moment iommu_free_table() only releases memory if
the table was initialized for the platform code use, i.e. it had
it_map initialized (which purpose is to track DMA memory space use).
With dynamic DMA windows, we will need to be able to release
iommu_table even if it was used for VFIO in which case it_map is NULL
so does the patch.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
| arch/powerpc/kernel/iommu.c | diffblobblamehistory |