[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, Mark Langsdorf <mark.langsdorf@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Thu, 30 Aug 2007 11:12:28 +0100
  • Delivery-date: Thu, 30 Aug 2007 03:13:13 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acfqh8RwaTy8r4iaT0y7Njlwu+54dgAROIeQAAbzeNkAABsToAABWQIj
  • Thread-topic: [Xen-devel] [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes

On 30/8/07 10:45, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> Sure, some experiment can be done later to compare dom0 userspace
> and in-xen governor. Agree that in-kernel dom0 approach is not
> charming because anyway it needs help from either user-level or xen
> for global view.
> 
> Actually finally we may take both. Xen takes simple heuristic policy
> with user-level governor to adjust with more complex and flexible
> policies based on domain behaviors. :-)

There is the problem, though, that most modern CPUs will need cpufreq info
to be parsed out of the ACPI DSDT. And Xen can't do that itself unaided.
Pushing down some form of cpufreq info table to Xen *is* an option though,
but we'd need more custom dom0 kernel code to do that. Or we'd need to do it
from a userspace program.

 -- Keir


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.