From: David Woodhouse <dwmw2@infradead.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: chrisw@redhat.com, aik@ozlabs.ru,
Joerg Roedel <joerg.roedel@amd.com>,
joro@8bytes.org, rusty@rustcorp.com.au, agraf@suse.de,
iommu@lists.linux-foundation.org, qemu-devel@nongnu.org,
B08248@freescale.com,
Alex Williamson <alex.williamson@redhat.com>,
scottwood@freescale.com, linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC] Device isolation infrastructure v2
Date: Mon, 19 Dec 2011 15:46:38 +0000 [thread overview]
Message-ID: <1324309598.2132.12.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20111219001125.GA30390@truffala.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Mon, 2011-12-19 at 11:11 +1100, David Gibson wrote:
> They have no inbuilt concept
> of domains (though we could fake in software in some circumstances).
That sentence doesn't make much sense to me.
Either you're saying that every device behind a given IOMMU is in *one*
domain (i.e. there's one domain per PCI host bridge), or you're saying
that each device has its *own* domain (maximum isolation, but still
perhaps not really true if you end up with PCIe-to-PCI bridges or broken
hardware such as the ones we've been discovering, where multifunction
devices do their DMA from the wrong function).
Either way, you *do* have domains. You just might not have thought about
it before.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5818 bytes --]
next prev parent reply other threads:[~2011-12-19 15:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 6:25 [Qemu-devel] [RFC] Device isolation infrastructure v2 David Gibson
2011-12-15 6:25 ` [Qemu-devel] [PATCH 1/3] device_isolation: Infrastructure for managing device isolation groups David Gibson
2011-12-15 6:25 ` [Qemu-devel] [PATCH 2/3] device_isolation: Support isolation on POWER p5ioc2 bridges David Gibson
2011-12-15 6:25 ` [Qemu-devel] [PATCH 3/3] device_isolation: Support isolation on POWER p7ioc (IODA) bridges David Gibson
2011-12-15 18:05 ` [Qemu-devel] [RFC] Device isolation infrastructure v2 Alex Williamson
2011-12-15 22:39 ` Alex Williamson
2011-12-16 1:40 ` David Gibson
2011-12-16 4:49 ` Alex Williamson
2011-12-16 6:00 ` David Gibson
2011-12-16 14:53 ` Joerg Roedel
2011-12-19 0:11 ` David Gibson
2011-12-19 15:41 ` Joerg Roedel
2011-12-21 3:32 ` David Gibson
2011-12-21 4:30 ` Alex Williamson
2011-12-21 6:12 ` Aaron Fabbri
2012-01-25 3:13 ` David Gibson
2012-01-25 23:44 ` Alex Williamson
2012-01-30 23:22 ` David Gibson
2011-12-21 16:46 ` Joerg Roedel
2011-12-19 15:46 ` David Woodhouse [this message]
2011-12-19 22:31 ` David Gibson
2011-12-19 22:56 ` David Woodhouse
2011-12-20 0:25 ` David Gibson
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=1324309598.2132.12.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=B08248@freescale.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=chrisw@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=scottwood@freescale.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).