[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd71a432-0799-3c07-4071-c79bce20a561@arm.com>
Date: Thu, 13 Jul 2017 10:29:42 +0100
From: Jean-Philippe Brucker <jean-philippe.brucker@....com>
To: "Michael S. Tsirkin" <mst@...hat.com>,
Will Deacon <will.deacon@....com>
Cc: Eric Auger <eric.auger@...hat.com>, eric.auger.pro@...il.com,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
robin.murphy@....com, christoffer.dall@...aro.org,
Marc.Zyngier@....com, alex.williamson@...hat.com, peterx@...hat.com
Subject: Re: [RFC 0/2] arm-smmu-v3 tlbi-on-map option
On 12/07/17 23:07, Michael S. Tsirkin wrote:
[...]
> I think using hardware support for nesting is the right final
> solution. It will take some time though. Given this, what should
> we do meanwhile?
>
> Assuming that's the final destination, a simple quirk like this
> seems to be preferable to virtio-iommu which we'll never be
> able to offload to hardware.
That's not entirely true. virtio-iommu will have an extension for hardware
nesting support. It was presented in my initial proposal, and I've made
significant progress since then.
Thanks,
Jean
Powered by blists - more mailing lists