[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 11 Nov 2016 12:42:23 +0100
From: Joerg Roedel <joro@...tes.org>
To: Auger Eric <eric.auger@...hat.com>
Cc: drjones@...hat.com, jason@...edaemon.net, kvm@...r.kernel.org,
marc.zyngier@....com, punit.agrawal@....com, will.deacon@....com,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
diana.craciun@....com, alex.williamson@...hat.com,
pranav.sawargaonkar@...il.com,
linux-arm-kernel@...ts.infradead.org, tglx@...utronix.de,
robin.murphy@....com, christoffer.dall@...aro.org,
eric.auger.pro@...il.com
Subject: Re: [RFC v2 8/8] iommu/arm-smmu: implement add_reserved_regions
callback
On Thu, Nov 10, 2016 at 07:00:52PM +0100, Auger Eric wrote:
> GICv2m and GICV3 ITS use dma-mapping iommu_dma_map_msi_msg to allocate
> an MSI IOVA on-demand.
Yes, and it the right thing to do there because as a DMA-API
implementation the dma-iommu code cares about the address space
allocation.
As I understand it this is different in your case, as someone else is
defining the address space layout. So why do you need to allocate it
yourself?
Joerg
Powered by blists - more mailing lists