[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170713204107-mutt-send-email-mst@kernel.org>
Date: Thu, 13 Jul 2017 20:44:38 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Jean-Philippe Brucker <jean-philippe.brucker@....com>
Cc: Will Deacon <will.deacon@....com>,
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 Thu, Jul 13, 2017 at 10:29:42AM +0100, Jean-Philippe Brucker wrote:
> 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
I don't recall seeing this.
Hardware specific extensions to virtio would be interesting, the
difficulty is in finding the balance between enabling minor quirks and
each vendor going their own way.
Is this the proposal you refer to?
https://www.spinics.net/lists/kvm/msg147990.html
I couldn't find any mention of nesting, it seems to
say that map requests are relayed through host.
--
MST
Powered by blists - more mailing lists