[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH][0/3] XenAPI: Add PCI Assignment Support



Hi all,

This series of patches is an attempt to support pci pass-through device
assignment via xen-api.

There already is 'PCI_bus' parameter in VM class to specify pci device
to be assigned, but it doesn't work now. Another problem is that pci
device hotplug/coldplug cannot be supported with the current model.

So I decided to implement fully-functional pci assignment support to
xen-api. Below is the basic design of new class models.

PPCI: Represents physical pci devices belonging to the host.
      ppci instances are automatically generated by xend and contain
      domain:bus:slot:func number, vendor name, device name and
      other information.
DPCI: Represents direct pci devices. dpci instances work as connectors
      between a vm and a physical pci device. Creation of a dpci device
      will result in attachment of the pci device and deletion will
      result in detachment.
+------------+ *      1 +----------+
|     VM     |----------|   host   |
+------------+          +----------+
    1 |                      | 1
      |                      |
    * |                      | *
+-------------+ 0,1   1 +----------+
|    DPCI     |---------|   PPCI   |
+-------------+         +----------+

BTW I'm aware that there is xen-api community project going on.
If there's any decision made about discussing/merging procedure of
xen-api related patches, please let me know.
Technical suggestions and comments are welcome, of course.

Regards,
-----------------------
Yosuke Iwamatsu
        NEC Corporation

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.