[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161110161331.GJ2078@8bytes.org>
Date: Thu, 10 Nov 2016 17:13:31 +0100
From: Joerg Roedel <joro@...tes.org>
To: Auger Eric <eric.auger@...hat.com>
Cc: eric.auger.pro@...il.com, christoffer.dall@...aro.org,
marc.zyngier@....com, robin.murphy@....com,
alex.williamson@...hat.com, will.deacon@....com,
tglx@...utronix.de, jason@...edaemon.net,
linux-arm-kernel@...ts.infradead.org, kvm@...r.kernel.org,
drjones@...hat.com, linux-kernel@...r.kernel.org,
pranav.sawargaonkar@...il.com, iommu@...ts.linux-foundation.org,
punit.agrawal@....com, diana.craciun@....com
Subject: Re: [RFC v2 8/8] iommu/arm-smmu: implement add_reserved_regions
callback
On Thu, Nov 10, 2016 at 04:57:51PM +0100, Auger Eric wrote:
> It does not only serve the purpose to register the MSI IOVA region. We
> also need to allocate an iova_domain where MSI IOVAs will be allocated
> upon the request of the relevant MSI controllers. Do you mean you don't
> like to use the iova allocator for this purpose?
Yes, it looks like the only purpose of iommu_get_dma_msi_region_cookie()
is to get the msi-region information into into the reserved-list.
Why do you need to 'allocate' the MSI region after all? Except for
IOMMU_DOMAIN_DMA domains the iommu-core code does not care about address
allocation. This is up to the users of the domain, which includes that
the user has to take care of the MSI region.
Besides that, 'iommu_get_dma_msi_region_cookie' is a terrible function
name and does not describe at all what the function does or is supposed
to do.
Joerg
Powered by blists - more mailing lists