Skip to content

Conversation

@tdavenvidia
Copy link
Collaborator

BugLink: https://bugs.launchpad.net/bugs/2119656

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: c404f55 ("iommu: Validate the PASID in iommu_attach_device_pasid()")
Cc: [email protected]

Reviewed-by: Lu Baolu [email protected]
Reviewed-by: Vasant Hegde [email protected]
Link: https://lore.kernel.org/r/[email protected]

(cherry picked from commit b3f6fcd)

Acked-by: Carol L Soto [email protected]
Acked-by: Matt Ochs [email protected]
Acked-by: Noah Wager [email protected]
Acked-by: Jacob Martin [email protected]

BugLink: https://bugs.launchpad.net/bugs/2119656

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: c404f55 ("iommu: Validate the PASID in iommu_attach_device_pasid()")
Cc: [email protected]
Signed-off-by: Tushar Dave <[email protected]>
Reviewed-by: Lu Baolu <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Joerg Roedel <[email protected]>
(cherry picked from commit b3f6fcd)
Signed-off-by: Nirmoy Das <[email protected]>
Acked-by: Carol L Soto <[email protected]>
Acked-by: Matt Ochs <[email protected]>
Acked-by: Noah Wager <[email protected]>
Acked-by: Jacob Martin <[email protected]>
Signed-off-by: Brad Figg <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant