WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH][0/3] XenAPI: Add PCI Assignment Support
From: Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>
Date: Thu, 10 Jul 2008 17:55:53 +0900
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 10 Jul 2008 01:56:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <486B6827.3090700@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <486B6827.3090700@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Windows/20080421)
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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel





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

<Prev in Thread] Current Thread [Next in Thread>