RE: [Xen-devel] separate domain info and vcpu context

To:	"Kip Macy" <kip.macy@xxxxxxxxx>
Subject:	RE: [Xen-devel] separate domain info and vcpu context
From:	"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date:	Sun, 8 May 2005 22:07:37 +0100
Cc:	xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Sun, 08 May 2005 21:07:16 +0000
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcVT+R/3ABigPGD1R5GxjklCkxNxLAAGJAbw
Thread-topic:	[Xen-devel] separate domain info and vcpu context

> Why should GETDOMAINCONTEXT also return the number of active VCPUs?

There's no need.

> That seems redundant. It would make more sense to me for it 
> to take exec_domain as an in/out variable. The value coming 
> in would be the index into the active CPUs and the out value 
> would be the actual vcpu number. So if you were running with 
> 4 vcpus but only the 4th vcpu was active, the caller would 
> set exec_domain to 0 and then xen would set exec_domain to 3.
> 
> I'd like to keep the number of iterations to 1, so just  to clarify
> - in GETDOMAININFO, exec_domain will be changed to out 
> variable n_active_vcpus, ctxt will be removed.

Yes.

> - GETDOMAINCONTEXT will have two fields, (u16)exec_domain 
> described above and  (vcpu_guest_context_t *)ctxt

Yes.

Ian

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

WARNING - OLD ARCHIVES

xen-devel

RE: [Xen-devel] separate domain info and vcpu context