From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: cpufreq status information Date: Mon, 08 Sep 2008 16:04:13 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" , Jan Beulich Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 8/9/08 15:49, "Tian, Kevin" 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