Re: [PATCH] iommu: Include MSI susceptibility to DMA in creating iommu groups

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Joerg Roedel (joro@xxxxxxxxxx) wrote:
> >From device standpoint a MSI transaction is always a DMA memory write
> to a given address range. The IOMMU-API should export a feature flag
> whether it supports filtering on those transaction or not. We have that
> today with the IOMMU_CAP_INTR_REMAP. I agree that the interface to get
> this information is ugly because a domain is needed. But the interface
> can be fixed. While doing this I suggest to rename that feature
> IOMMU_CAP_INTR_ISOLATION or something like that.
> VFIO can then check for this flag on module-load and refuse to load if
> it is not available.

I can see that the native grouping (the typical pci bridge type) is
really more a property of the topology.

The isolation properties of a group (arguably the whole point of the
group) is subtly different.

Leaves the questions:

What is the value of a group w/out complete isolation?
Is there a practical problem w/ conflating the subtleties above?

thanks,
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux