From: Priya <pbhat@acis.ufl.edu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Xen timing mode
Date: Tue, 23 Feb 2010 15:49:10 -0500 [thread overview]
Message-ID: <5c3550fe1002231249u16da3cccw124682598be464ba@mail.gmail.com> (raw)
In-Reply-To: <4B843A6A.5050102@goop.org>
[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]
Thank you very much!
On Tue, Feb 23, 2010 at 3:28 PM, Jeremy Fitzhardinge <jeremy@goop.org>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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 1679 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-02-23 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 16:50 Xen timing mode PBhat
2010-02-23 17:08 ` Keir Fraser
2010-02-23 17:12 ` Priya
2010-02-23 17:18 ` Keir Fraser
2010-02-23 17:29 ` Priya
2010-02-23 17:33 ` Priya
2010-02-23 20:28 ` Jeremy Fitzhardinge
2010-02-23 20:49 ` Priya [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c3550fe1002231249u16da3cccw124682598be464ba@mail.gmail.com \
--to=pbhat@acis.ufl.edu \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).