[Xen-devel] separate domain info and vcpu context

To:	xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] separate domain info and vcpu context
From:	Kip Macy <kip.macy@xxxxxxxxx>
Date:	Fri, 29 Apr 2005 11:15:01 -0700
Delivery-date:	Fri, 29 Apr 2005 18:14:43 +0000
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=sJOQhl+6rLUKe2vp+KLgKej/yTT9oDUIi0rWmxCceDURQQkmRINEzrjnoCzPFifGmkrSiVeRVfvA01yzPPybo5e0n/J/gsrQE6zCepovovcD/XuTXb4Mxn3btO/72nK4Th9LLGxea9Ifac062LuZkGWWRHQcSodI5CEHSuE0b8o=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to:	Kip Macy <kip.macy@xxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Might it make sense to to add a separate hypercall for getting a
vcpu's context?  It would be cleaner from my standpoint to have
exec_domain be an OUT variable that indicates the number of vcpus in
use. It seems a bit odd getting generic info for a domain and then
specific context for one of the vcpus.


      -Kip

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