Skip to content

Commit 1a14bf0

Browse files
Jacob Panjoergroedel
authored andcommitted
iommu/sva: Use GFP_KERNEL for pasid allocation
We’re not using spinlock-protected IOASID allocation anymore, there’s no need for GFP_ATOMIC. Reviewed-by: Kevin Tian <kevin.tian@intel.com> Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com> Link: https://lore.kernel.org/r/20230322200803.869130-6-jacob.jun.pan@linux.intel.com Signed-off-by: Joerg Roedel <jroedel@suse.de>
1 parent 4e14176 commit 1a14bf0

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

drivers/iommu/iommu-sva.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,8 @@ static int iommu_sva_alloc_pasid(struct mm_struct *mm, ioasid_t min, ioasid_t ma
2828
goto out;
2929
}
3030

31-
ret = ida_alloc_range(&iommu_global_pasid_ida, min, max, GFP_ATOMIC);
32-
if (ret < 0)
31+
ret = ida_alloc_range(&iommu_global_pasid_ida, min, max, GFP_KERNEL);
32+
if (ret < min)
3333
goto out;
3434
mm->pasid = ret;
3535
ret = 0;

0 commit comments

Comments
 (0)