[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161110151848.GE2078@8bytes.org>
Date: Thu, 10 Nov 2016 16:18:48 +0100
From: Joerg Roedel <joro@...tes.org>
To: Robin Murphy <robin.murphy@....com>
Cc: Don Dutile <ddutile@...hat.com>, Will Deacon <will.deacon@....com>,
Alex Williamson <alex.williamson@...hat.com>,
Christoffer Dall <christoffer.dall@...aro.org>,
Eric Auger <eric.auger@...hat.com>, eric.auger.pro@...il.com,
marc.zyngier@....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,
benh@...nel.crashing.org, arnd@...db.de, jcm@...hat.com,
dwmw@...zon.co.uk
Subject: Re: Summary of LPC guest MSI discussion in Santa Fe
On Wed, Nov 09, 2016 at 08:11:16PM +0000, Robin Murphy wrote:
> When we *are* in full control of the IOVA space, we just carve out what
> we can find as best we can - see iova_reserve_pci_windows() in
> dma-iommu.c, which isn't really all that different to what x86 does
> (e.g. init_reserved_iova_ranges() in amd-iommu.c).
Yeah, that code was actually written with a look at what the Intel
driver does. I don't really like that it goes over all resources and
reserves them individually (not only because it is not hotplug-safe).
I have to check whether there is a nice and generic way to find out the
root-bridge windows and just reserve them in the iova-space. That would
be easier and more reliable.
Joerg
Powered by blists - more mailing lists