WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen timing mode

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Xen timing mode
From: Priya <pbhat@xxxxxxxxxxxx>
Date: Tue, 23 Feb 2010 15:49:10 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 23 Feb 2010 12:49:40 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=0n93SHlrNQ7uRA6hf2Qf+quyzQ8/zTaLrZWH+bTpspg=; b=p4TwJwUBs/5WYBvOIVBTRAWjHHHcQtvubupjSTF20O+jDpcU5QDP1PApKVE6Wouknr gVvCxgtWEPkxJ4kisaw3UKs2ui7y9+HxN3Fh8Q+va7I9W4/BSY5z6xSwQkX6q0QjV/Q/ 2JnofK2CgyxRttF8X2zA3JUyhS6dlKeroIjlg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=GveLDNadRPW9uTb+gi3ZowCyGEPvKCkfVgNlmGvhEA400zz9eB6OYb41ekuDhOD/lh 5ZbWNNQPp9khhmBBYJ9u2x7yK+3XJLb2WdhIh+UG3qDA5sna3qvVDgiNrkB+KjmEp6mj lsEpbV9KGL24qUMxY+isiOVUejM/ZzzqNfqFE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B843A6A.5050102@xxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <5c3550fe1002230912j1a5d0650oa1e355652c8e3062@xxxxxxxxxxxxxx> <C7A9BE50.B018%keir.fraser@xxxxxxxxxxxxx> <5c3550fe1002230929r37d1bd73mdd82fc84ee51d0fd@xxxxxxxxxxxxxx> <4B843A6A.5050102@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thank you very much!



On Tue, Feb 23, 2010 at 3:28 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
On 02/23/2010 09:29 AM, Priya wrote:
The Xen Interface manual for Xen v2.0 (attached) Page 4 defines Domain - virtual time as

" The time that progresses at the same pace as system time, but only while a domain is executing -- it stops while a domain is de-scheduled. Therefore the share of the CPU that a domain receives is indicated by the rate at which its virtual time increases."

I am interesting in finding out if any of the timing system calls/instructions like gettimeofday(), hwclock(), rdtsc() can read this domain virtual time.

/proc/stat publishes stolen time for each vcpu (second-last column on the "cpuX" lines); you can subtract that from monotonic time to work out how much vcpu the domain has got.


   J

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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>