diff options
| author | Sebastian Andrzej Siewior <[email protected]> | 2018-03-22 15:22:41 +0000 |
|---|---|---|
| committer | Joerg Roedel <[email protected]> | 2018-03-29 08:38:17 +0000 |
| commit | 2cd1083d79a0a8c223af430ca97884c28a1e2fc0 (patch) | |
| tree | 02b576c3fd3c6c9726cd6cab987f96acf2d68aa7 /fs/proc/array.c | |
| parent | iommu/amd: Drop the lock while allocating new irq remap table (diff) | |
| download | kernel-2cd1083d79a0a8c223af430ca97884c28a1e2fc0.tar.gz kernel-2cd1083d79a0a8c223af430ca97884c28a1e2fc0.zip | |
iommu/amd: Make amd_iommu_devtable_lock a spin_lock
Before commit 0bb6e243d7fb ("iommu/amd: Support IOMMU_DOMAIN_DMA type
allocation") amd_iommu_devtable_lock had a read_lock() user but now
there are none. In fact, after the mentioned commit we had only
write_lock() user of the lock. Since there is no reason to keep it as
writer lock, change its type to a spin_lock.
I *think* that we might even be able to remove the lock because all its
current user seem to have their own protection.
Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
Signed-off-by: Joerg Roedel <[email protected]>
Diffstat (limited to 'fs/proc/array.c')
0 files changed, 0 insertions, 0 deletions