From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Will Deacon <will.deacon@arm.com>
Cc: Eric Auger <eric.auger@redhat.com>,
eric.auger.pro@gmail.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, robin.murphy@arm.com,
christoffer.dall@linaro.org, Marc.Zyngier@arm.com,
alex.williamson@redhat.com, peterx@redhat.com
Subject: Re: [RFC 0/2] arm-smmu-v3 tlbi-on-map option
Date: Thu, 13 Jul 2017 10:29:42 +0100 [thread overview]
Message-ID: <fd71a432-0799-3c07-4071-c79bce20a561@arm.com> (raw)
In-Reply-To: <20170712223654-mutt-send-email-mst@kernel.org>
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
next prev parent reply other threads:[~2017-07-13 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 15:15 Eric Auger
2017-07-09 15:15 ` [RFC 1/2] iommu/io-pgtable-arm: flush TLBs when IO_PGTABLE_QUIRK_TLBI_ON_MAP Eric Auger
2017-07-09 15:15 ` [RFC 2/2] arm-smmu-v3: Add tlbi_on_map option Eric Auger
2017-07-12 17:54 ` [RFC 0/2] arm-smmu-v3 tlbi-on-map option Will Deacon
2017-07-12 22:07 ` Michael S. Tsirkin
2017-07-13 9:29 ` Jean-Philippe Brucker [this message]
2017-07-13 17:44 ` Michael S. Tsirkin
2017-07-13 19:17 ` Jean-Philippe Brucker
2017-07-13 20:29 ` Michael S. Tsirkin
2017-07-26 14:41 ` Auger Eric
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd71a432-0799-3c07-4071-c79bce20a561@arm.com \
--to=jean-philippe.brucker@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=robin.murphy@arm.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®