Messages in this thread | | | From | "Tian, Kevin" <> | Subject | RE: [PATCH 1/4] iommu/vt-d: Implement set device pasid op for default domain | Date | Fri, 3 Mar 2023 05:38:19 +0000 |
| |
> From: Baolu Lu <baolu.lu@linux.intel.com> > Sent: Thursday, March 2, 2023 10:07 PM > > > + > > + if (hw_pass_through && domain_type_is_si(dmar_domain)) > > + ret = intel_pasid_setup_pass_through(iommu, dmar_domain, > > + dev, pasid); > > + else if (dmar_domain->use_first_level) > > + ret = domain_setup_first_level(iommu, dmar_domain, > > + dev, pasid); > > + else > > + ret = intel_pasid_setup_second_level(iommu, dmar_domain, > > + dev, pasid); > > + > > + return ret; > > +} > > Do you need to consider pasid cache invalidation? >
To avoid confusion this is not about invalidation of pasid cache itself which should be covered by above setup functions already.
Here actually means per-PASID invalidation in iotlb and devtlb. Today only RID is tracked per domain for invalidation. it needs extension to walk attached pasid too.
| |