From: David Gibson <david@gibson.dropbear.id.au>
To: alex.williamson@redhat.com
Cc: aik@ozlabs.ru, benh@kernel.crashing.org, joerg.roedel@amd.com,
dwmw2@infradead.org, chrisw@redhat.com, agraf@suse.de,
scottwood@freescale.com, B08248@freescale.com,
rusty@rustcorp.com.au, iommu@lists.linux-foundation.org,
qemu-devel@nongnu.org, linux-kernel@vger.kernel.org
Subject: [RFC] Device isolation infrastructure v2
Date: Thu, 15 Dec 2011 17:25:37 +1100 [thread overview]
Message-ID: <1323930340-24055-1-git-send-email-david@gibson.dropbear.id.au> (raw)
Here's the second spin of my preferred approach to handling grouping
of devices for safe assignment to guests.
Changes since v1:
* Many name changes and file moves for improved consistency
* Bugfixes and cleanups
* The interface to the next layer up is considerably fleshed out,
although it still needs work.
* Example initialization of groups for p5ioc2 and p7ioc.
TODO:
* Need sample initialization of groups for intel and/or amd iommus
* Use of sysfs attributes to control group permission is probably a
mistake. Although it seems a bit odd, registering a chardev for
each group is probably better, because perms can be set from udev
rules, just like everything else.
* Need more details of what the binder structure will need to
contain.
* Handle complete removal of groups.
* Clarify what will need to happen on the hot unplug path.
next reply other threads:[~2011-12-15 6:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 6:25 David Gibson [this message]
2011-12-15 6:25 ` [PATCH 1/3] device_isolation: Infrastructure for managing device isolation groups David Gibson
2011-12-15 6:25 ` [PATCH 2/3] device_isolation: Support isolation on POWER p5ioc2 bridges David Gibson
2011-12-15 6:25 ` [PATCH 3/3] device_isolation: Support isolation on POWER p7ioc (IODA) bridges David Gibson
2011-12-15 18:05 ` [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 ` [Qemu-devel] " 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
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=1323930340-24055-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=B08248@freescale.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=chrisw@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--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).