From: David Woodhouse <dwmw2@infradead.org>
To: Andy Lutomirski <luto@amacapital.net>, Theodore Ts'o <tytso@mit.edu>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Paolo Bonzini <pbonzini@redhat.com>,
m.smarduch@samsung.com
Subject: Re: [Ksummit-discuss] Short topic: virtio vs IOMMU
Date: Mon, 26 Oct 2015 13:31:18 +0900 [thread overview]
Message-ID: <1445833878.3405.24.camel@infradead.org> (raw)
In-Reply-To: <CALCETrWJveWdcHy7N0gE_KeZb3TUbSGSQUVy4YjKGpb5p94yXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
On Sun, 2015-10-25 at 19:55 -0700, Andy Lutomirski wrote:
> It would be nice to nail down how virtio should interact with IOMMUs
> on the emulated busses. A bunch of the relevant maintainers are
> around, and a short slot for this topic might make sense.
>
> The goal would be to figure out how to accomplish something like this
> series:
>
> https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=vi
> rtio_ring_xen
>
> but in a way that would actually work on all supported platforms
> without breaking backward compatibility or killing performance.
FWIW it should be fine with VT-d; we already cope with the concept that
*some* devices don't have translation, while others do. If we don't
have DMA translation for the virtio devices, that works out fine.
I think the main problem is on POWER where they don't yet have that
option.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2015-10-26 4:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 2:55 Andy Lutomirski
2015-10-26 4:31 ` David Woodhouse [this message]
2015-10-26 4:43 ` Joerg Roedel
2015-10-26 4:48 ` David Woodhouse
2015-10-26 5:04 ` Joerg Roedel
2015-10-26 5:13 ` David Woodhouse
2015-10-26 5:20 ` Joerg Roedel
2015-10-26 6:03 ` Andy Lutomirski
2015-10-26 4:38 ` Joerg Roedel
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=1445833878.3405.24.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@amacapital.net \
--cc=m.smarduch@samsung.com \
--cc=pbonzini@redhat.com \
--cc=tytso@mit.edu \
/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