[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB5276A1920E24BE91CF1FD2098C112@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Tue, 23 Apr 2024 09:01:17 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>, Joerg Roedel <joro@...tes.org>, "Will
Deacon" <will@...nel.org>, Robin Murphy <robin.murphy@....com>, "Jason
Gunthorpe" <jgg@...pe.ca>
CC: "Zhang, Tina" <tina.zhang@...el.com>, "Liu, Yi L" <yi.l.liu@...el.com>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 01/12] iommu/vt-d: Add cache tag assignment interface
> From: Lu Baolu <baolu.lu@...ux.intel.com>
> Sent: Tuesday, April 16, 2024 4:07 PM
>
> @@ -1757,6 +1759,9 @@ int domain_attach_iommu(struct dmar_domain
> *domain, struct intel_iommu *iommu)
> unsigned long ndomains;
> int num, ret = -ENOSPC;
>
> + if (domain->domain.type == IOMMU_DOMAIN_SVA)
> + return 0;
> +
> info = kzalloc(sizeof(*info), GFP_KERNEL);
> if (!info)
> return -ENOMEM;
> @@ -1804,6 +1809,9 @@ void domain_detach_iommu(struct dmar_domain
> *domain, struct intel_iommu *iommu)
> {
> struct iommu_domain_info *info;
>
> + if (domain->domain.type == IOMMU_DOMAIN_SVA)
> + return;
> +
> spin_lock(&iommu->lock);
> info = xa_load(&domain->iommu_array, iommu->seq_id);
> if (--info->refcnt == 0) {
above two are not called for SVA. Why do they start checking
SVA type now?
Powered by blists - more mailing lists