[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> 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


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.