From: Yi Liu <yi.l.liu@intel.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
Kevin Tian <kevin.tian@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>, Vinod Koul <vkoul@kernel.org>,
"Fenghua Yu" <fenghuay@nvidia.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Zhou Wang <wangzhou1@hisilicon.com>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH v2 02/12] iommu/vt-d: Check if SVA is supported when attaching the SVA domain
Date: Tue, 4 Mar 2025 15:44:44 +0800 [thread overview]
Message-ID: <5969af0c-8ad9-40f9-a6b7-aece0d408816@intel.com> (raw)
In-Reply-To: <20250224051627.2956304-3-baolu.lu@linux.intel.com>
On 2025/2/24 13:16, Lu Baolu wrote:
> From: Jason Gunthorpe <jgg@nvidia.com>
>
> Attach of a SVA domain should fail if SVA is not supported, move the check
> for SVA support out of IOMMU_DEV_FEAT_SVA and into attach.
>
> Also check when allocating a SVA domain to match other drivers.
>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> ---
> drivers/iommu/intel/iommu.c | 37 +------------------------------
> drivers/iommu/intel/svm.c | 43 +++++++++++++++++++++++++++++++++++++
> 2 files changed, 44 insertions(+), 36 deletions(-)
>
Reviewed-by: Yi Liu <yi.l.liu@intel.com>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index cc46098f875b..a4048de66378 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -3851,41 +3851,6 @@ static struct iommu_group *intel_iommu_device_group(struct device *dev)
> return generic_device_group(dev);
> }
>
> -static int intel_iommu_enable_sva(struct device *dev)
> -{
> - struct device_domain_info *info = dev_iommu_priv_get(dev);
> - struct intel_iommu *iommu;
> -
> - if (!info || dmar_disabled)
> - return -EINVAL;
> -
> - iommu = info->iommu;
> - if (!iommu)
> - return -EINVAL;
> -
> - if (!(iommu->flags & VTD_FLAG_SVM_CAPABLE))
> - return -ENODEV;
> -
> - if (!info->pasid_enabled || !info->ats_enabled)
> - return -EINVAL;
> -
> - /*
> - * Devices having device-specific I/O fault handling should not
> - * support PCI/PRI. The IOMMU side has no means to check the
> - * capability of device-specific IOPF. Therefore, IOMMU can only
> - * default that if the device driver enables SVA on a non-PRI
> - * device, it will handle IOPF in its own way.
> - */
> - if (!info->pri_supported)
> - return 0;
> -
> - /* Devices supporting PRI should have it enabled. */
> - if (!info->pri_enabled)
> - return -EINVAL;
> -
> - return 0;
> -}
> -
> static int context_flip_pri(struct device_domain_info *info, bool enable)
> {
> struct intel_iommu *iommu = info->iommu;
> @@ -4006,7 +3971,7 @@ intel_iommu_dev_enable_feat(struct device *dev, enum iommu_dev_features feat)
> return intel_iommu_enable_iopf(dev);
>
> case IOMMU_DEV_FEAT_SVA:
> - return intel_iommu_enable_sva(dev);
> + return 0;
>
> default:
> return -ENODEV;
> diff --git a/drivers/iommu/intel/svm.c b/drivers/iommu/intel/svm.c
> index f5569347591f..ba93123cb4eb 100644
> --- a/drivers/iommu/intel/svm.c
> +++ b/drivers/iommu/intel/svm.c
> @@ -110,6 +110,41 @@ static const struct mmu_notifier_ops intel_mmuops = {
> .free_notifier = intel_mm_free_notifier,
> };
>
> +static int intel_iommu_sva_supported(struct device *dev)
> +{
> + struct device_domain_info *info = dev_iommu_priv_get(dev);
> + struct intel_iommu *iommu;
> +
> + if (!info || dmar_disabled)
> + return -EINVAL;
> +
> + iommu = info->iommu;
> + if (!iommu)
> + return -EINVAL;
> +
> + if (!(iommu->flags & VTD_FLAG_SVM_CAPABLE))
> + return -ENODEV;
> +
> + if (!info->pasid_enabled || !info->ats_enabled)
> + return -EINVAL;
> +
> + /*
> + * Devices having device-specific I/O fault handling should not
> + * support PCI/PRI. The IOMMU side has no means to check the
> + * capability of device-specific IOPF. Therefore, IOMMU can only
> + * default that if the device driver enables SVA on a non-PRI
> + * device, it will handle IOPF in its own way.
> + */
> + if (!info->pri_supported)
> + return 0;
> +
> + /* Devices supporting PRI should have it enabled. */
> + if (!info->pri_enabled)
> + return -EINVAL;
> +
> + return 0;
> +}
> +
> static int intel_svm_set_dev_pasid(struct iommu_domain *domain,
> struct device *dev, ioasid_t pasid,
> struct iommu_domain *old)
> @@ -121,6 +156,10 @@ static int intel_svm_set_dev_pasid(struct iommu_domain *domain,
> unsigned long sflags;
> int ret = 0;
>
> + ret = intel_iommu_sva_supported(dev);
> + if (ret)
> + return ret;
> +
> dev_pasid = domain_add_dev_pasid(domain, dev, pasid);
> if (IS_ERR(dev_pasid))
> return PTR_ERR(dev_pasid);
> @@ -161,6 +200,10 @@ struct iommu_domain *intel_svm_domain_alloc(struct device *dev,
> struct dmar_domain *domain;
> int ret;
>
> + ret = intel_iommu_sva_supported(dev);
> + if (ret)
> + return ERR_PTR(ret);
> +
> domain = kzalloc(sizeof(*domain), GFP_KERNEL);
> if (!domain)
> return ERR_PTR(-ENOMEM);
--
Regards,
Yi Liu
next prev parent reply other threads:[~2025-03-04 7:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 5:16 [PATCH v2 00/12] iommu: Remove IOMMU_DEV_FEAT_SVA/_IOPF Lu Baolu
2025-02-24 5:16 ` [PATCH v2 01/12] iommu/arm-smmu-v3: Put iopf enablement in the domain attach path Lu Baolu
2025-02-24 5:16 ` [PATCH v2 02/12] iommu/vt-d: Check if SVA is supported when attaching the SVA domain Lu Baolu
2025-02-25 7:23 ` Tian, Kevin
2025-03-04 7:44 ` Yi Liu [this message]
2025-02-24 5:16 ` [PATCH v2 03/12] iommu: Remove IOMMU_DEV_FEAT_SVA Lu Baolu
2025-02-25 7:24 ` Tian, Kevin
2025-03-04 7:50 ` Yi Liu
2025-02-24 5:16 ` [PATCH v2 04/12] iommu/vt-d: Move scalable mode ATS enablement to probe path Lu Baolu
2025-02-25 7:28 ` Tian, Kevin
2025-02-26 2:21 ` Baolu Lu
2025-03-04 7:55 ` Yi Liu
2025-02-24 5:16 ` [PATCH v2 05/12] iommu/vt-d: Move PRI enablement in " Lu Baolu
2025-02-25 7:37 ` Tian, Kevin
2025-02-26 3:53 ` Baolu Lu
2025-02-24 5:16 ` [PATCH v2 06/12] iommu/vt-d: Cleanup intel_context_flush_present() Lu Baolu
2025-02-25 7:43 ` Tian, Kevin
2025-02-26 3:57 ` Baolu Lu
2025-02-26 5:17 ` Tian, Kevin
2025-03-04 8:43 ` Yi Liu
2025-03-05 2:21 ` Baolu Lu
2025-03-05 3:34 ` Yi Liu
2025-03-05 5:36 ` Baolu Lu
2025-02-24 5:16 ` [PATCH v2 07/12] iommu/vt-d: Put iopf enablement in domain attach path Lu Baolu
2025-02-25 8:02 ` Tian, Kevin
2025-02-24 5:16 ` [PATCH v2 08/12] iommufd/selftest: " Lu Baolu
2025-02-25 8:16 ` Tian, Kevin
2025-02-26 4:06 ` Baolu Lu
2025-02-24 5:16 ` [PATCH v2 09/12] dmaengine: idxd: Remove unnecessary IOMMU_DEV_FEAT_IOPF Lu Baolu
2025-02-25 8:16 ` Tian, Kevin
2025-02-24 5:16 ` [PATCH v2 10/12] uacce: " Lu Baolu
2025-02-24 10:00 ` Zhangfei Gao
2025-02-25 8:17 ` Tian, Kevin
2025-02-24 5:16 ` [PATCH v2 11/12] iommufd: " Lu Baolu
2025-02-25 8:18 ` Tian, Kevin
2025-02-24 5:16 ` [PATCH v2 12/12] iommu: Remove iommu_dev_enable/disable_feature() Lu Baolu
2025-02-25 8:18 ` Tian, Kevin
2025-02-24 9:58 ` [PATCH v2 00/12] iommu: Remove IOMMU_DEV_FEAT_SVA/_IOPF Zhangfei Gao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5969af0c-8ad9-40f9-a6b7-aece0d408816@intel.com \
--to=yi.l.liu@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=fenghuay@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vkoul@kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=zhangfei.gao@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®