From: Carsten Schiers <carsten@schiers.de>
To: xen-devel@lists.xensource.com
Subject: Question on xenpm
Date: Mon, 5 Jul 2010 11:09:23 +0200 [thread overview]
Message-ID: <25029217.31278320963140.JavaMail.root@uhura> (raw)
Dear all,
after having upgraded my server from AMD 4050e to X4 640, I now use cpufreq=xen and had
to adapt a munin script (monitoring tool) to display the residency in the different P-states.
This script uses /sys/device/system/cpu/cpu0/cpufreq to read out the information, whereas
I now use xenpm get-cpufreq-state.
Before I noticed that the CPU is in highest possible P-state (lowest frequences) nearly all
of the time, and a minimal percentage in the lowest. Now I can see a 50/50 distribution.
Interesting enough, the xenpm get-cpuidle-state will show that the CPUs are at aprox. 90%
in C1 idle state.
Can there be a difference in how the two methods to collect the info are working? I mean
something like xenpm will not count residency when in C1, but cpufreq driver will normaly
do?
BR,
Carsten.
next reply other threads:[~2010-07-05 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 9:09 Carsten Schiers [this message]
2010-07-05 11:05 ` AW: Question on xenpm Carsten Schiers
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=25029217.31278320963140.JavaMail.root@uhura \
--to=carsten@schiers.de \
--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).