From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>, Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: cpufreq status information
Date: Mon, 08 Sep 2008 16:04:13 +0100 [thread overview]
Message-ID: <C4EAFD7D.26E77%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F024D9768@pdsmsx412.ccr.corp.intel.com>
On 8/9/08 15:49, "Tian, Kevin" <kevin.tian@intel.com> wrote:
>> The advantage of the latter is that the frequency changes are
>> interleaved
>> with other stuff you care about, like what's being scheduled,
>> what's on run
>> queues etc. Since obviously frequency information all by
>> itself is not so
>> interesting.
>>
>
> Yes, we already have many examples within dom0 to retrieve xen
> specific information bypassing dom0. By the way, we have the plan
> to add xentrace events for all processor PM stuff, including freq
> change and also cpu idle states transition (like break causes, etc.)
It's good to know there are other users and developers of xentrace!
-- Keir
next prev parent reply other threads:[~2008-09-08 15:04 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
2008-09-08 14:35 ` Keir Fraser
2008-09-08 14:49 ` Tian, Kevin
2008-09-08 15:04 ` Keir Fraser [this message]
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=C4EAFD7D.26E77%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jbeulich@novell.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.