Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1279136

Re: [PATCH V5 RESEND 2/3] iommu/hisilicon: Add hi6220-SoC smmu driver

Show all headers | View raw

On Sat, Nov 28, 2015 at 10:19:14AM +0800, chenfeng wrote:
> On 2015/11/27 20:02, Joerg Roedel wrote:
> > You need to create an iommu-group per smmu in your system and put all
> > devices translated by this smmu in that group. And then you must change
> > your code to allow attaching/detaching this iommu-group to different
> > domains.
> > 
> I read the code,I am confused about these concepts.
> In my opinion,
> IOMMU-Domain: The masters in one domain share the same iova space. Is that right?

Yes, an iommu-domain is an abstraction of a single page-table and
describes one iova address space. The SMMU in your hardware supports
only on page-table, so all devices behind it share a single iova address
space, und must be in the same domain.

But the way you implemented it there could be only one domain per SMMU.
With the IOMMU-API we must support to change the domain of an SMMU.
Think of one domain for DMA-API usage and another for VFIO, for example.

> IOMMU-GROUP: As you mentioned up,all devices translated by this smmu
> should be into one group.  I can do this. But if there is only on
> domain in the system, how can I attaching/detaching the group to
> different domains.

IOMMU-groups describe the isolation capabilities of the IOMMU between
devices. If devices are in a different IOMMU-group, this means that
the hardware can isolate them from each other.

Attaching the devices in a group to a new domain means in your case,
that you set a different page-table for them. Since you can only do that
for all devices behind a SMMU, these devices must be in on IOMMU-group.



	Joerg

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH V5 RESEND 0/3] Add iommu support for hi6220 HiKey board Chen Feng <puck.chen@hisilicon.com> - 2015-11-20 03:30 +0100
  [PATCH V5 RESEND 3/3] arm64: dts: Add dts node for hi6220 smmu driver Chen Feng <puck.chen@hisilicon.com> - 2015-11-20 03:30 +0100
  [PATCH V5 RESEND 2/3] iommu/hisilicon: Add hi6220-SoC smmu driver Chen Feng <puck.chen@hisilicon.com> - 2015-11-20 03:30 +0100
    Re: [PATCH V5 RESEND 2/3] iommu/hisilicon: Add hi6220-SoC smmu driver Joerg Roedel <joro@8bytes.org> - 2015-11-27 13:10 +0100
      Re: [PATCH V5 RESEND 2/3] iommu/hisilicon: Add hi6220-SoC smmu driver chenfeng <puck.chen@hisilicon.com> - 2015-11-28 03:20 +0100
        Re: [PATCH V5 RESEND 2/3] iommu/hisilicon: Add hi6220-SoC smmu driver Joerg Roedel <joro@8bytes.org> - 2015-11-28 13:30 +0100
  [PATCH V5 RESEND 1/3] docs: iommu: Documentation for iommu in hi6220 SoC Chen Feng <puck.chen@hisilicon.com> - 2015-11-20 03:30 +0100
    Re: [PATCH V5 RESEND 1/3] docs: iommu: Documentation for iommu in  hi6220 SoC Rob Herring <robh@kernel.org> - 2015-11-20 15:30 +0100
  Re: [PATCH V5 RESEND 0/3] Add iommu support for hi6220 HiKey board Joerg Roedel <joro@8bytes.org> - 2015-11-27 12:50 +0100
    Re: [PATCH V5 RESEND 0/3] Add iommu support for hi6220 HiKey board chenfeng <puck.chen@hisilicon.com> - 2015-11-28 03:20 +0100

csiph-web