ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	m.smarduch@samsung.com,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Short topic: virtio vs IOMMU
Date: Mon, 26 Oct 2015 06:04:50 +0100	[thread overview]
Message-ID: <20151026050450.GF27420@8bytes.org> (raw)
In-Reply-To: <1445834882.3405.30.camel@infradead.org>

On Mon, Oct 26, 2015 at 01:48:02PM +0900, David Woodhouse wrote:
> It would be useful to have an emulated IOMMU, full stop. And yeah, it
> might actually make sense to *start* by using it for purely virtual
> devices, [...]

Sure, I think this is what qemu provides already, except for the virtio
devices (which are also emulated). I think it would be cool to have
virtio translated by the emulated iommu too (at least optional).

> [...] and then graduate to doing it for passthrough (which will
> finally mean we can stop having to pin *all* guest memory the moment we
> assign a device, and we only have to pin those pages which are
> referenced from the IOMMU page tables).

Good point, havn't thought of that yet. But getting rid of the excessive
pinning this way would be really great.



	Joerg

  reply	other threads:[~2015-10-26  5:04 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
2015-10-26  4:43   ` Joerg Roedel
2015-10-26  4:48     ` David Woodhouse
2015-10-26  5:04       ` Joerg Roedel [this message]
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=20151026050450.GF27420@8bytes.org \
    --to=joro@8bytes.org \
    --cc=dwmw2@infradead.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=m.smarduch@samsung.com \
    --cc=pbonzini@redhat.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