This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Sat, 1 Sep 2007 22:14:11 +0800
Delivery-date: Sat, 01 Sep 2007 07:14:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2FF2E6D.D26A%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <D470B4E54465E3469E2ABBC5AFAC390F013B21B8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C2FF2E6D.D26A%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acfqh8RwaTy8r4iaT0y7Njlwu+54dgAROIeQAAbzeNkAABsToAABWQIjAB9V6qAAErBLqwAKHGtwAAEaJJoAEo/UwAAWs08+AATSlUAAASGChAAAQkbQ
Thread-topic: [Xen-devel] [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes
>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年9月1日 21:58
>While I'm hassling you about C states: are there any examples in real
>of available C states changing dynamically? I mean, it makes sense to
>that available power/frequency combinations may change in response to
>something like AC power being removed (this may make higher
>options unavailable). But why would available C states change? I
>these states were implemented internally on the CPU, and so are either
>universally available or not, and I don't see any physical explanation for
>why available deep-sleep options would be affected by e.g., battery vs.
> -- Keir

I have to say that I didn't think it carefully before. Following is the 
description about _CST from ACPI spec (

The platform may change the number or type of C States available 
for OSPM use dynamically by issuing a Notify events on the processor 
object with a notification value of 0x81. This will cause OSPM to 
re-evaluate any _CST object residing under the processor object 
notified. For example, the platform might notify OSPM that the number 
of supported C States has changed as a result of an asynchronous AC 
insertion / removal event.

Maybe some hardware people know the tricks inside. :-(


Xen-devel mailing list