[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [RFC] Device isolation infrastructure v2
From: |
David Gibson |
Subject: |
[Qemu-devel] [RFC] Device isolation infrastructure v2 |
Date: |
Thu, 15 Dec 2011 17:25:37 +1100 |
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.
- [Qemu-devel] [RFC] Device isolation infrastructure v2,
David Gibson <=
- [Qemu-devel] [PATCH 2/3] device_isolation: Support isolation on POWER p5ioc2 bridges, David Gibson, 2011/12/15
- [Qemu-devel] [PATCH 1/3] device_isolation: Infrastructure for managing device isolation groups, David Gibson, 2011/12/15
- [Qemu-devel] [PATCH 3/3] device_isolation: Support isolation on POWER p7ioc (IODA) bridges, David Gibson, 2011/12/15
- Re: [Qemu-devel] [RFC] Device isolation infrastructure v2, Alex Williamson, 2011/12/15
- Re: [Qemu-devel] [RFC] Device isolation infrastructure v2, Joerg Roedel, 2011/12/16