Hi Bjorn,
On 1/5/22 1:06 AM, Bjorn Helgaas wrote:
On Tue, Jan 04, 2022 at 09:56:39AM +0800, Lu Baolu wrote:
If a switch lacks ACS P2P Request Redirect, a device below the switch can
bypass the IOMMU and DMA directly to other devices below the switch, so
all the downstream devices must be in the same IOMMU group as the switch
itself.
Help me think through what's going on here. IIUC, we put devices in
the same IOMMU group when they can interfere with each other in any
way (DMA, config access, etc).
(We said "DMA" above, but I guess this would also apply to config
requests, right?)
I am not sure whether devices could interfere each other through config
space access. The IOMMU hardware only protects and isolates DMA
accesses, so that userspace could control DMA directly. The config
accesses will always be intercepted by VFIO. Hence, I don't see a
problem.
*This* patch doesn't check for any ACS features. Can you connect the
dots for me? I guess the presence or absence of P2P Request Redirect
determines the size of the IOMMU group. And the following says
It's done in iommu core (drivers/iommu/iommu.c):
/*
* Use standard PCI bus topology, isolation features, and DMA alias quirks
* to find or create an IOMMU group for a device.
*/
struct iommu_group *pci_device_group(struct device *dev)
something about what is allowed in the group? And .no_kernel_api_dma
allows an exception to the general rule?
Yes.
The pci_dma_configure() marks the iommu_group as containing only devices
with kernel drivers that manage DMA. Avoid this default behavior for the
portdrv driver in order for compatibility with the current vfio policy.
I assume "IOMMU group" means the same as "iommu_group"; maybe we can
use one of them consistently?
Sure.
Best regards,
baolu
