 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] separate domain info and vcpu context
| To: | Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] separate domain info and vcpu context |
| From: | Kip Macy <kip.macy@xxxxxxxxx> |
| Date: | Sun, 8 May 2005 11:09:41 -0700 |
| Cc: | xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
| Delivery-date: | Sun, 08 May 2005 18:09:16 +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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NKVwi0GOl0/c0qkxA7g2rDTHVPVEqdy8BizPr5jLdVBjMDigVKascihrbAwqghAfGXL3wECi+OoQ50mc/ODqT7XW0W+vAkMXC19+dzXb/DkA7b8XQy6Yy1t9iXLH5O/W2d61AXOWK9T1Hj6Uf3xeyKdCpsekMfPXoudBYEzkT1A= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <A95E2296287EAD4EB592B5DEEFCE0E9D1E3E17@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| 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> |
| References: | <A95E2296287EAD4EB592B5DEEFCE0E9D1E3E17@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | Kip Macy <kip.macy@xxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
> I would like both calls to return the number of VCPUs in use, but we
> still want the 'give me VCPU x or the next active one if it doesn't
> exist' enumeration scheme since VCPUs can potentially be sparse. Go for
> it!
>
Why should GETDOMAINCONTEXT also return the number of active VCPUs?
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.
- GETDOMAINCONTEXT will have two fields, (u16)exec_domain described
above and (vcpu_guest_context_t *)ctxt
Thanks.
-Kip
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] Re: Interdomain comms, Harry Butterworth |
|---|---|
| Next by Date: | Re: [Xen-devel] PCI interrupt setup failure: gateway, Jonathan S. Shapiro |
| Previous by Thread: | [Xen-devel] A question on frame_list, Pradheep K E |
| Next by Thread: | Re: [Xen-devel] separate domain info and vcpu context, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
