[Xen-cim] Allocation Capabilities struct

To:	<xen-cim@xxxxxxxxxxxxxxxxxxx>, "Gareth S Bestor" <bestorga@xxxxxxxxxx>, "Jim Fehlig" <jfehlig@xxxxxxxxxx>
Subject:	[Xen-cim] Allocation Capabilities struct
From:	"Szymanski, Lukasz K" <Lukasz.Szymanski@xxxxxxxxxx>
Date:	Mon, 11 Dec 2006 12:55:30 -0500
Delivery-date:	Mon, 11 Dec 2006 10:07:38 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id:	xen-cim mailing list <xen-cim.lists.xensource.com>
List-post:	<mailto:xen-cim@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AccdTYxJdIunvsfwRoiYcLDMGRzOag==
Thread-topic:	Allocation Capabilities struct

I am trying to determine the proper way of resolving what goes into the RESOURCE and RESOURCES structs for the allocation capabilities stuff. I do not believe Xen needs to be accessed in any way, so a counter like currentCapabilityNum should be the only member of this struct. The RESROUCE structure should be something like this:

typedef struct {
   char instanceid[1024];
   int ResourceType;
   int RequestTypesSupported;
   int SharingMode;
} _RESOURCE;

Please let me know if this is on the right track.

Luke

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

WARNING - OLD ARCHIVES

xen-cim

[Xen-cim] Allocation Capabilities struct