From: Sheng Yang <sheng@linux.intel.com>
To: kvm@vger.kernel.org
Cc: "Saksena, Abhishek" <abhishek.saksena@intel.com>
Subject: Re: KVM Virtual CPU time profiling
Date: Fri, 22 Jan 2010 10:38:47 +0800 [thread overview]
Message-ID: <201001221038.47885.sheng@linux.intel.com> (raw)
In-Reply-To: <4158487B9DEE0647BA23911D1C22795712F2245FDB@orsmsx501.amr.corp.intel.com>
On Friday 22 January 2010 02:41:35 Saksena, Abhishek wrote:
> Hi All,
> Is there a way in KVM to measure the real physical (CPU) time consumed by
> each running Virtual CPU? (I want to do time profiling of the virtual
> machines running on host system)
>
> Also, is there an explanation somewhere on how Virtual CPU scheduling is
> achieved in KVM? Thanks
Each VM is a QEmu process, and each vcpu is a thread of it(but not all the
threads are vcpus). Currently the KVM related scheduler algorithm is the same
as other host threads/processes.
You can get thread_id for each vcpu in QEmu monitor, by:
(qemu) info cpus
Then, you can do anything you want with it, e.g. using top to got each
thread/vcpu's CPU time. :)
--
regards
Yang, Sheng
prev parent reply other threads:[~2010-01-22 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 18:41 KVM Virtual CPU time profiling Saksena, Abhishek
2010-01-22 2:38 ` Sheng Yang [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=201001221038.47885.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=abhishek.saksena@intel.com \
--cc=kvm@vger.kernel.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