lkml.org 
[lkml]   [2023]   [Apr]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v5 3/7] iommu: Move global PASID allocation from SVA to core
Date
> From: Jacob Pan <jacob.jun.pan@linux.intel.com>
> Sent: Friday, April 28, 2023 1:50 AM
>
> Devices that use Intel ENQCMD to submit work must use global PASIDs in
> that the PASID are stored in a per CPU MSR. When such device need to
> submit work for in-kernel DMA with PASID, it must allocate PASIDs from
> the same global number space to avoid conflict.

well the device itself cannot submit work to itself. It's software to
submit work to the device. 😊

> /* Allocate a PASID for the mm within range (inclusive) */
> -static int iommu_sva_alloc_pasid(struct mm_struct *mm, ioasid_t min,
> ioasid_t max)
> +static int iommu_sva_alloc_pasid(struct mm_struct *mm, struct device *dev)
> {
> int ret = 0;
>
> - if (!pasid_valid(min) || !pasid_valid(max) ||
> - min == 0 || max < min)
> - return -EINVAL;
> -
> mutex_lock(&iommu_sva_lock);
> /* Is a PASID already associated with this mm? */
> - if (pasid_valid(mm->pasid)) {
> - if (mm->pasid < min || mm->pasid > max)
> - ret = -EOVERFLOW;
> + if (pasid_valid(mm->pasid))
> goto out;

emmm here you still want to check whether mm->pasid exceeds
the max pasid width of the bound device.

\
 
 \ /
  Last update: 2023-04-28 11:47    [W:0.112 / U:1.632 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site