From: Vasant Hegde <vasant.hegde@amd.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: linux-pci@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 rc] iommu: Skip PASID validation for devices without PASID capability
Date: Mon, 5 May 2025 17:03:42 +0530 [thread overview]
Message-ID: <cb579c8f-a9a0-4ed0-b0ec-77282fc82806@amd.com> (raw)
In-Reply-To: <5b74482c-38c3-4720-81b8-67c599184e39@nvidia.com>
On 5/2/2025 2:30 AM, Tushar Dave wrote:
>
>
> On 5/1/25 03:58, Vasant Hegde wrote:
>> On 4/30/2025 8:24 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 v2:
>>> - added no-pasid check in __iommu_set_group_pasid and __iommu_remove_group_pasid
>>>
>>> drivers/iommu/iommu.c | 22 ++++++++++++++++------
>>> 1 file changed, 16 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
>>> index 60aed01e54f2..8251b07f4022 100644
>>> --- a/drivers/iommu/iommu.c
>>> +++ b/drivers/iommu/iommu.c
>>> @@ -3329,8 +3329,9 @@ static int __iommu_set_group_pasid(struct iommu_domain
>>> *domain,
>>> int ret;
>>
>> initialize ret to zero?
>
> Thanks Vasant.
>
> How about:
>
> for_each_group_device(group, device) {
> - ret = domain->ops->set_dev_pasid(domain, device->dev,
> - pasid, NULL);
> - if (ret)
> - goto err_revert;
> + if (device->dev->iommu->max_pasids > 0) {
> + ret = domain->ops->set_dev_pasid(domain, device->dev,
> + pasid, NULL);
> + if (ret)
> + goto err_revert;
> + }
> }
>
> Let me know.
Looks good.
-Vasant
prev parent reply other threads:[~2025-05-05 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 2:54 [PATCH v2 rc] iommu: Skip PASID validation for devices without PASID capability Tushar Dave
2025-05-01 4:17 ` Baolu Lu
2025-05-01 10:58 ` Vasant Hegde
2025-05-01 21:00 ` Tushar Dave
2025-05-05 11:33 ` Vasant Hegde [this message]
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=cb579c8f-a9a0-4ed0-b0ec-77282fc82806@amd.com \
--to=vasant.hegde@amd.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