From: gavin <gbtux@126.com>
To: xen-devel@lists.xen.org
Subject: How to get or measure the scheduled time of a VM accurately?
Date: Tue, 30 Oct 2012 23:44:01 +0800 (CST) [thread overview]
Message-ID: <50df9b92.3204f.13ab257fc59.Coremail.gbtux@126.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 650 bytes --]
Hi,
I have some questions on the Xen credit scheduler.
In the Xen credit scheduler, a VM is scheduled to run a certain time. This time maybe last for 30ms or less if the VM was preempted. So how can I get this time of a VM accurately? In the source code (xen/common/sched_credit.c) file, the method csched_schedule returns a task_slice. Can I use the task_slice.time as the accurate scheduled time of a VM？
I also want to know the accurate scheduled time of a VM in a period of time, such as 10 seconds. So, how can get it? Is there any useful tool can do this for me?
Looking forward to your reply. Thank you very much.
Best Regards,
Gavin
[-- Attachment #1.2: Type: text/html, Size: 1300 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
reply other threads:[~2012-10-30 15:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50df9b92.3204f.13ab257fc59.Coremail.gbtux@126.com \
--to=gbtux@126.com \
--cc=xen-devel@lists.xen.org \
/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).