Thread (36 messages) 36 messages, 5 authors, 2017-07-25

[PATCH 1/5] iommu: Add capability IOMMU_CAP_BYPASS

From: Will Deacon <hidden>
Date: 2017-07-19 11:23:15
Also in: kvm, linux-iommu, lkml

On Wed, Jul 19, 2017 at 04:49:00PM +0530, Anup Patel wrote:
On Wed, Jul 19, 2017 at 4:28 PM, Robin Murphy [off-list ref] wrote:
quoted
On 19/07/17 10:33, Anup Patel wrote:
quoted
Some of the IOMMUs (such as ARM SMMU) are capable of bypassing
transactions for which no IOMMU domain is configured.

This patch adds IOMMU_CAP_BYPASS which can be used by IOMMU
drivers to advertise transation bypass capability of an IOMMU.
Whatever the intended semantics of this are, I can't help thinking it
would be better served by allowing callers to explicitly allocate their
own IOMMU_DOMAIN_IDENTITY domains. That would also be useful for the
problem we have with legacy virtio devices behind real IOMMUs.
We want to use VFIO no-IOMMU mode for FlexRM device but
currently it does not allow on our SOC because IOMMU ops are
registered for platform bus.
Why do you want to use no-IOMMU mode if you have an IOMMU, and why you do
think the individual IOMMU drivers are the place to implement this?

NAK to the SMMU patches, for the reasons outlined by Robin.

Will
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help