Yosuke Iwamatsu
2008-Jul-02 11:36 UTC
[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@lists.xensource.com
http://lists.xensource.com/xen-devel
Yosuke Iwamatsu
2008-Jul-10 08:55 UTC
[Xen-devel] [PATCH][0/3] XenAPI: Add PCI Assignment Support
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Yosuke Iwamatsu
2008-Jul-28 09:04 UTC
[Xen-API] [PATCH] Update Document ([PATCH][0/3] XenAPI: Add PCI Assignment Support)
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_______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api