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

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

[Yosuke Iwamatsu]

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

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

[Yosuke Iwamatsu]

Keir,

Now that you applied this patch set, is it okay to update the xen-api
document toward xen-3.3 release? I'm a little concerned about api
stability, but if the basic structure of these new classes is
acceptable, I'm willing to renew the document accordingly.

Thanks,
-- Yosuke

Yosuke Iwamatsu wrote:
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel

[PATCH] Update Document ([PATCH][0/3] XenAPI: Add PCI Assignment Support)

[Yosuke Iwamatsu]

[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

Here is the patch to update the xen-api doc for pci device assignment
support.

Thank you,
-----------------
  Yosuke Iwamatsu

Yosuke Iwamatsu wrote:
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel


[-- Attachment #2: xenapi_pci_doc.patch --]
[-- Type: all/allfiles, Size: 31200 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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