From: Baolu Lu <baolu.lu@linux.intel.com>
To: Tushar Dave <tdave@nvidia.com>,
joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
kevin.tian@intel.com, jgg@nvidia.com, yi.l.liu@intel.com,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: baolu.lu@linux.intel.com, linux-pci@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v4 rc] iommu: Skip PASID validation for devices without PASID capability
Date: Tue, 20 May 2025 17:12:46 +0800 [thread overview]
Message-ID: <b8ab3c01-0602-4980-8c31-0d16c5de2545@linux.intel.com> (raw)
In-Reply-To: <20250520011937.3230557-1-tdave@nvidia.com>
On 5/20/2025 9:19 AM, Tushar Dave wrote:
> Generally PASID support requires ACS settings that usually create
> single device groups, but there are some niche cases where we can get
> multi-device groups and still have working PASID support. The primary
> issue is that PCI switches are not required to treat PASID tagged TLPs
> specially so appropriate ACS settings are required to route all TLPs to
> the host bridge if PASID is going to work properly.
>
> pci_enable_pasid() does check that each device that will use PASID has
> the proper ACS settings to achieve this routing.
>
> However, no-PASID devices can be combined with PASID capable devices
> within the same topology using non-uniform ACS settings. In this case
> the no-PASID devices may not have strict route to host ACS flags and
> end up being grouped with the PASID devices.
>
> This configuration fails to allow use of the PASID within the iommu
> core code which wrongly checks if the no-PASID device supports PASID.
>
> Fix this by ignoring no-PASID devices during the PASID validation. They
> will never issue a PASID TLP anyhow so they can be ignored.
>
> Fixes: c404f55c26fc ("iommu: Validate the PASID in iommu_attach_device_pasid()")
> Cc:stable@vger.kernel.org
> Signed-off-by: Tushar Dave<tdave@nvidia.com>
> ---
>
> changes in v4:
> - rebase to 6.15-rc7
>
> drivers/iommu/iommu.c | 43 ++++++++++++++++++++++++++++---------------
> 1 file changed, 28 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 4f91a740c15f..9d728800a862 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -3366,10 +3366,12 @@ static int __iommu_set_group_pasid(struct iommu_domain *domain,
> int ret;
>
> for_each_group_device(group, device) {
> - ret = domain->ops->set_dev_pasid(domain, device->dev,
> - pasid, old);
> - if (ret)
> - goto err_revert;
> + if (device->dev->iommu->max_pasids > 0) {
> + ret = domain->ops->set_dev_pasid(domain, device->dev,
> + pasid, old);
> + if (ret)
> + goto err_revert;
> + }
You can save an indent by making it like this,
for_each_group_device(group, device) {
if (device->dev->iommu->max_pasids == 0)
continue;
ret = domain->ops->set_dev_pasid(domain, device->dev, pasid, old);
if (ret)
goto err_revert;
}
Anyway,
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
next prev parent reply other threads:[~2025-05-20 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 1:19 Tushar Dave
2025-05-20 8:53 ` Vasant Hegde
2025-05-20 9:12 ` Baolu Lu [this message]
2025-05-22 7:10 ` Joerg Roedel
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=b8ab3c01-0602-4980-8c31-0d16c5de2545@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=tdave@nvidia.com \
--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
all inboxes | Powered by JetHome®