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

[Xen-devel] cpu specific fields in getdomaininfo

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Sun, 8 May 2005 17:11:55 -0700
Delivery-date: Mon, 09 May 2005 00:11:30 +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=VcLWGIoOLWGaCU2GqLDkkmkdGvtpAQanjYNQIYaQz31JG0gPnTtdy1WjGucddBn7bTjQK9ganvTjlBq+yBcJG2KZs2f8E1BUtBJTpu0Mw0xUAMZJJ68qbg/YBk81S7qHLH1VlMQOrUFXX1MbiDvZDaPy3HME4PHuc0Bs3v/k65U=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'd like to know what you're recommendations are for cpu_time,
processor, and per-exec_domain flags.

>From my usage standpoint, cpu_time should be the highest of all of the
vcpus, PAUSED and BLOCKED should be the logical AND of all the vcpus
and RUNNING should be the logical OR of all of the vcpus, processor
should simply be moved to getvcpucontext or be made into separate
field along the lines of the bitmask discussed previously.

Thanks.
     -Kip

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

Follow-Ups:
- Re: [Xen-devel] cpu specific fields in getdomaininfo
  - From: Keir Fraser

Prev by Date: Re: [Xen-devel] semantics of GETDOMAININFO
Next by Date: RE: [Xen-devel] kernel panic with ipv6 in Xen
Previous by thread: [Xen-devel] semantics of GETDOMAININFO
Next by thread: Re: [Xen-devel] cpu specific fields in getdomaininfo
Index(es):
- Date
- Thread

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