From: "Michael S. Tsirkin" <mst@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
David Woodhouse <dwmw2@infradead.org>,
Wei Liu <wei.liu2@citrix.com>,
Alex Williamson <alex.williamson@redhat.com>,
peterx@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Amit Shah <amit.shah@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jason Wang <jasowang@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH RFC] fixup! virtio: convert to use DMA api
Date: Tue, 19 Apr 2016 19:04:43 +0300 [thread overview]
Message-ID: <20160419190314-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <CALCETrVBo-XBD53eStOCwJd53F7_VTnrMJ9rY7_cXwnt2Z6AOw@mail.gmail.com>
On Tue, Apr 19, 2016 at 09:00:27AM -0700, Andy Lutomirski wrote:
> On Apr 19, 2016 2:13 AM, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >
> >
> > I guess you are right in that we should split this part out.
> > What I wanted is really the combination
> > PASSTHROUGH && !PLATFORM so that we can say "ok we don't
> > need to guess, this device actually bypasses the IOMMU".
>
> What happens when you use a device like this on Xen or with a similar
> software translation layer?
I think you don't use it on Xen since virtio doesn't bypass an IOMMU there.
If you do you have misconfigured your device.
--
MST
prev parent reply other threads:[~2016-04-19 16:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 11:47 [Qemu-devel] [PATCH RFC] fixup! virtio: convert to use DMA api Michael S. Tsirkin
2016-04-18 11:58 ` David Woodhouse
2016-04-18 13:12 ` Michael S. Tsirkin
2016-04-18 14:03 ` David Woodhouse
2016-04-18 14:23 ` Michael S. Tsirkin
2016-04-18 15:22 ` David Woodhouse
2016-04-18 15:30 ` Michael S. Tsirkin
2016-04-18 15:51 ` David Woodhouse
2016-04-18 16:27 ` Michael S. Tsirkin
2016-04-18 18:29 ` David Woodhouse
2016-04-18 19:24 ` Andy Lutomirski
2016-04-19 10:27 ` Michael S. Tsirkin
2016-04-19 16:02 ` Andy Lutomirski
2016-04-19 16:09 ` Michael S. Tsirkin
2016-04-19 16:12 ` Andy Lutomirski
2016-04-19 16:20 ` Michael S. Tsirkin
2016-04-19 16:26 ` David Woodhouse
2016-04-19 17:49 ` Michael S. Tsirkin
2016-04-19 18:01 ` Andy Lutomirski
2016-04-19 20:16 ` Michael S. Tsirkin
2016-04-19 20:27 ` Andy Lutomirski
2016-04-19 20:54 ` Michael S. Tsirkin
2016-04-19 21:07 ` Andy Lutomirski
2016-04-20 13:14 ` Michael S. Tsirkin
2016-04-20 15:43 ` Andy Lutomirski
2016-04-19 9:13 ` Michael S. Tsirkin
2016-04-19 14:44 ` Alex Williamson
2016-04-19 16:00 ` Andy Lutomirski
2016-04-19 16:04 ` Michael S. Tsirkin [this message]
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=20160419190314-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dwmw2@infradead.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wei.liu2@citrix.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;
as well as URLs for NNTP newsgroup(s).