From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Kevin Tian <kevin.tian@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: cpufreq status information
Date: Mon, 08 Sep 2008 15:30:48 +0100 [thread overview]
Message-ID: <48C55338.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C4EAEE9F.26E60%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 08.09.08 16:00 >>>
>After all, guest performance is at least as affected by CPU (and other
>resources) contention from other guests as it is by power-management
>governors in the hyeprvisor. Indeed, if the governors are doing their job
>right then guest performance should not be considerably impacted by them
>even in absolute terms.
Right you say 'if' - what if not? How do I tell, especially when I can't touch
the system and easily put a patched hypervisor and/or kernel on. If we
get a complaint from a customer that he thinks frequency scaling doesn't
do what it's expected to, we'll need to have a simple mechanism at hand
to determine what's going on with his box.
And even for development purposes I think a one-look proof that things
work as expected is quite useful (I'm doing the same for a few other basic
things - the interrupt rate being one of those that helped spot problems
that otherwise would have gone unnoticed for a much longer period of
time).
Jan
next prev parent reply other threads:[~2008-09-08 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 13:12 cpufreq status information Jan Beulich
2008-09-08 13:22 ` Tian, Kevin
2008-09-08 13:33 ` Jan Beulich
2008-09-08 13:50 ` Tian, Kevin
2008-09-08 14:00 ` Keir Fraser
2008-09-08 14:13 ` Tian, Kevin
2008-09-08 14:30 ` Jan Beulich [this message]
2008-09-08 14:35 ` Keir Fraser
2008-09-08 14:49 ` Tian, Kevin
2008-09-08 15:04 ` Keir Fraser
2008-09-08 14:57 ` Tian, Kevin
2008-09-08 14:23 ` Jan Beulich
2008-09-08 14:42 ` Tian, Kevin
2008-09-08 13:38 ` Keir Fraser
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=48C55338.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=kevin.tian@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.