From: Arnd Bergmann <arnd@arndb.de>
To: Caitlin Bestler <caitlinb@broadcom.com>
Cc: kvm-devel@lists.sourceforge.net,
xen-devel <xen-devel@lists.xensource.com>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [kvm-devel] [Xen-devel] More virtio users
Date: Wed, 13 Jun 2007 01:54:26 +0200 [thread overview]
Message-ID: <200706130154.27513.arnd@arndb.de> (raw)
In-Reply-To: <1EF1E44200D82B47BD5BA61171E8CE9D04269608@NT-IRVA-0750.brcm.ad.broadcom.com>
On Wednesday 13 June 2007, Caitlin Bestler wrote:
>
> > It can be done, but you'd also need a passthrough for the
> > IOMMU in that case, and you get a potential security hole: if
> > a malicious guest is smart enough to figure out IOMMU
> > mappings from the device to memory owned by the host.
> >
> If it is possible for a malicious guess to use the IOMMU
> to access memory that was not assigned to it then either
> the Hypervisor is not really a Hypervisor or the IOMMU
> is not really an IOMMU.
Unfortunately, most IOMMU implementations are not really
IOMMUs then, I guess ;-). To be safe, every PCI device
needs to have its own tagged DMA transfers, which essentially
boils down to having each device behind a separate PCI
host bridge, and that's not very likely to be done
on PC style hardware.
Admittedly, I haven't seen many IOMMU implementations, but
the one I'm most familiar with (the one on the Cell
Broadband Engine) can only assign a local device on the
north bridge to one guest in a secure way, but an
entire PCI or PCIe host is treated as a single device
when seen from the IOMMU, so when one PCIe device has
a mapping to guest A, guest B can use MMIO access to
program another device on the same host to do DMA
into the buffer provided by guest A.
Arnd <><
next parent reply other threads:[~2007-06-12 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1EF1E44200D82B47BD5BA61171E8CE9D04269608@NT-IRVA-0750.brcm.ad.broadcom.com>
2007-06-12 23:54 ` Arnd Bergmann [this message]
2007-06-13 5:28 ` [kvm-devel] [Xen-devel] More virtio users Muli Ben-Yehuda
2007-06-14 19:41 ` Caitlin Bestler
[not found] <200706150139.36770.arnd@arndb.de>
2007-06-15 16:26 ` Caitlin Bestler
[not found] <1EF1E44200D82B47BD5BA61171E8CE9D04269D6E@NT-IRVA-0750.brcm.ad.broadcom.com>
2007-06-14 23:39 ` Arnd Bergmann
[not found] <466BA965.6050208@qumranet.com>
[not found] ` <20070610080602.GD3738@rhun.haifa.ibm.com>
[not found] ` <466BB1AF.1000601@qumranet.com>
2007-06-12 22:07 ` Arnd Bergmann
2007-06-12 23:40 ` Caitlin Bestler
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=200706130154.27513.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=caitlinb@broadcom.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.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).