From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
iommu@lists.linux.dev, Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@nvidia.com>, Joerg Roedel <joro@8bytes.org>,
dmaengine@vger.kernel.org, vkoul@kernel.org
Cc: baolu.lu@linux.intel.com, Will Deacon <will@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Raj Ashok <ashok.raj@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Tony Luck <tony.luck@intel.com>,
"Zanussi, Tom" <tom.zanussi@intel.com>
Subject: Re: [PATCH v4 5/7] iommu/vt-d: Make device pasid attachment explicit
Date: Mon, 10 Apr 2023 11:14:49 +0800 [thread overview]
Message-ID: <3e431fa5-c056-5b79-32f5-185c5980a678@linux.intel.com> (raw)
In-Reply-To: <54591e4f-682b-cd4e-ee6b-9c9395d9c526@linux.intel.com>
On 4/10/23 10:46 AM, Baolu Lu wrote:
>> @@ -4040,6 +4100,7 @@ static void device_block_translation(struct
>> device *dev)
>> spin_lock_irqsave(&info->domain->lock, flags);
>> list_del(&info->link);
>> + info->dev_attached = 0;
>> spin_unlock_irqrestore(&info->domain->lock, flags);
>> domain_detach_iommu(info->domain, iommu);
>> @@ -4186,7 +4247,7 @@ static int intel_iommu_attach_device(struct
>> iommu_domain *domain,
>> if (ret)
>> return ret;
>> - return dmar_domain_attach_device(to_dmar_domain(domain), dev);
>> + return dmar_domain_attach_device_pasid(to_dmar_domain(domain),
>> dev, PASID_RID2PASID);
>> }
>
> For VT-d driver, attach_dev and attach_dev_pasid have different
> meanings. Merging them into one helper may lead to confusion. What do
> you think of the following code? The dmar_domain_attach_device_pasid()
> helper could be reused for attach_dev_pasid path.
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 7c2f4bd33582..09ae62bc3724 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -2434,6 +2434,40 @@ static int __init si_domain_init(int hw)
> return 0;
> }
>
> +
> +static int dmar_domain_attach_device_pasid(struct dmar_domain *domain,
> + struct intel_iommu *iommu,
> + struct device *dev, ioasid_t pasid)
> +{
> + struct device_pasid_info *dev_pasid;
> + unsigned long flags;
> + int ret;
> +
> + dev_pasid = kzalloc(sizeof(*dev_pasid), GFP_KERNEL);
> + if (!dev_pasid)
> + return -ENOMEM;
> +
> + if (hw_pass_through && domain_type_is_si(domain))
> + ret = intel_pasid_setup_pass_through(iommu, domain, dev, pasid);
> + else if (domain->use_first_level)
> + ret = domain_setup_first_level(iommu, domain, dev, pasid);
> + else
> + ret = intel_pasid_setup_second_level(iommu, domain, dev, pasid);
> +
> + if (ret) {
> + kfree(dev_pasid);
> + return ret;
> + }
> +
> + dev_pasid->pasid = pasid;
> + dev_pasid->dev = dev;
> + spin_lock_irqsave(&domain->lock, flags);
> + list_add(&dev_pasid->link_domain, &domain->dev_pasids);
> + spin_unlock_irqrestore(&domain->lock, flags);
> +
> + return 0;
> +}
> +
> static int dmar_domain_attach_device(struct dmar_domain *domain,
> struct device *dev)
> {
> @@ -2458,15 +2492,8 @@ static int dmar_domain_attach_device(struct
> dmar_domain *domain,
> /* PASID table is mandatory for a PCI device in scalable mode. */
> if (sm_supported(iommu) && !dev_is_real_dma_subdevice(dev)) {
> /* Setup the PASID entry for requests without PASID: */
> - if (hw_pass_through && domain_type_is_si(domain))
> - ret = intel_pasid_setup_pass_through(iommu, domain,
> - dev, PASID_RID2PASID);
> - else if (domain->use_first_level)
> - ret = domain_setup_first_level(iommu, domain, dev,
> - PASID_RID2PASID);
> - else
> - ret = intel_pasid_setup_second_level(iommu, domain,
> - dev, PASID_RID2PASID);
> + ret = dmar_domain_attach_device_pasid(domain, iommu, dev,
> + PASID_RID2PASID);
> if (ret) {
> dev_err(dev, "Setup RID2PASID failed\n");
> device_block_translation(dev);
Sorry! I forgot one thing. The dev_pasid data allocated in attach_dev
path should be freed in device_block_translation(). Perhaps we need to
add below change?
@@ -4107,6 +4134,7 @@ static void device_block_translation(struct device
*dev)
{
struct device_domain_info *info = dev_iommu_priv_get(dev);
struct intel_iommu *iommu = info->iommu;
+ struct device_pasid_info *dev_pasid;
unsigned long flags;
iommu_disable_pci_caps(info);
@@ -4118,6 +4146,16 @@ static void device_block_translation(struct
device *dev)
domain_context_clear(info);
}
+ spin_lock_irqsave(&info->domain->lock, flags);
+ list_for_each_entry(dev_pasid, &domain->dev_pasids, link_domain) {
+ if (dev_pasid->dev != dev || dev_pasid->pasid != RID2PASID)
+ continue;
+
+ list_del(&dev_pasid->link_domain);
+ kfree(dev_pasid);
+ }
+ spin_unlock_irqrestore(&info->domain->lock, flags);
+
if (!info->domain)
return;
Best regards,
baolu
next prev parent reply other threads:[~2023-04-10 3:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 18:05 [PATCH v4 0/7] Re-enable IDXD kernel workqueue under DMA API Jacob Pan
2023-04-07 18:05 ` [PATCH v4 1/7] iommu/vt-d: Use non-privileged mode for all PASIDs Jacob Pan
2023-04-07 18:05 ` [PATCH v4 2/7] iommu/vt-d: Remove PASID supervisor request support Jacob Pan
2023-04-07 18:05 ` [PATCH v4 3/7] iommu: Support allocation of global PASIDs outside SVA Jacob Pan
2023-04-10 1:34 ` Baolu Lu
2023-04-11 8:02 ` Tian, Kevin
2023-04-12 1:37 ` Baolu Lu
2023-04-17 16:46 ` Jacob Pan
2023-04-18 2:06 ` Baolu Lu
2023-04-18 23:04 ` Jacob Pan
2023-04-19 2:40 ` Baolu Lu
2023-04-19 21:05 ` Jacob Pan
2023-04-17 16:07 ` Jacob Pan
2023-04-07 18:05 ` [PATCH v4 4/7] iommu/vt-d: Reserve RID_PASID from global PASID space Jacob Pan
2023-04-10 1:59 ` Baolu Lu
2023-04-17 16:36 ` Jacob Pan
2023-04-07 18:05 ` [PATCH v4 5/7] iommu/vt-d: Make device pasid attachment explicit Jacob Pan
2023-04-10 2:46 ` Baolu Lu
2023-04-10 3:14 ` Baolu Lu [this message]
2023-04-18 21:32 ` Jacob Pan
2023-04-19 2:26 ` Baolu Lu
2023-04-07 18:05 ` [PATCH v4 6/7] iommu/vt-d: Implement set_dev_pasid domain op Jacob Pan
2023-04-07 18:05 ` [PATCH v4 7/7] dmaengine/idxd: Re-enable kernel workqueue under DMA API Jacob Pan
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=3e431fa5-c056-5b79-32f5-185c5980a678@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=tom.zanussi@intel.com \
--cc=tony.luck@intel.com \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
/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
Powered by JetHome