From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yosuke Iwamatsu Subject: [PATCH][0/3] XenAPI: Add PCI Assignment Support Date: Wed, 02 Jul 2008 20:36:07 +0900 Message-ID: <486B6827.3090700@ab.jp.nec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com, xen-api@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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