WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "Rik van Riel" <riel@xxxxxxxxxx>, "Keir Fraser" <keir@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Fri, 31 Aug 2007 10:43:18 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
Delivery-date: Thu, 30 Aug 2007 19:43:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46D70B20.2010108@xxxxxxxxxx>
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: <C2FC9B0B.150B9%keir@xxxxxxxxxxxxx> <46D70B20.2010108@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfrMuh87PbljvX3R22xBFUNaDX5cwARauHw
Thread-topic: [Xen-devel] [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes
>From: Rik van Riel [mailto:riel@xxxxxxxxxx]
>Sent: 2007年8月31日 2:23
>
>Keir Fraser wrote:
>
>> It's a misleading simplification. For example, the ondemand governor
>will
>> build and run in a dom0 kernel but it's not actually going to do the right
>> thing, as it doesn't observe whole-machine load.
>
>Here is the missing piece of the puzzle.   A platform
>hypercall operation to get system wide idle time.
>
>I believe Mark's changes, together with this little
>patch, are the way we can get cpufreq working on
>Xen with the minimal amount of code duplication.
>
>Duplicating code anywhere, whether it be inside the
>hypervisor or in some Xen-only userland package, will
>only lead to bit rot and make Xen maintenance more
>painful.
>
>Signed-off-by: Rik van Riel <riel@xxxxxxxxxx>
>

The run_state info is not accurate for other vcpus not on current 
processor, since it's only updated when switching out.

Thanks,
Kevin

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>