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

RE: [Xen-devel] [PATCH][Retry 1] 4/4: cpufreq/PowerNow! in Xen: PowerNow! changes


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
  • Date: Fri, 31 Aug 2007 11:56:15 -0500
  • Delivery-date: Fri, 31 Aug 2007 09:57:17 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acfr5NmmGClNJFfYEdySawAX8io7RQACpUAw
  • Thread-topic: [Xen-devel] [PATCH][Retry 1] 4/4: cpufreq/PowerNow! in Xen: PowerNow! changes

> On 30/8/07 18:01, "Mark Langsdorf" <mark.langsdorf@xxxxxxx> wrote:
> 
> > Patch 4 covers the changes necessary to the PowerNow! driver
> > to make it correctly associate shared cores under Xen.
> 
> Should we have a copy of that file in powernow-k8-xen.c? Can 
> the patched file work correctly in a native Linux build?

The patch is the same patch I submitted upstream for the native
2.6.23 Linux kernel.  

In native mode, the kernel creates a cpumask for each cpu that
lists its sibling cores.  Unfortunately, Xen doesn't do that.
The patch instead reads and parses the _PSD ACPI structure,
which indicates which cores share pstates with other cores.  
(Frankly, _PSD is the right way to do it, but the other way
was easier until Linux got ACPI support for _PSD).  If Xen
were using the same kernel version as Linux, the patch wouldn't
be necessary.

-Mark Langsdorf
Operating System Research Center
AMD



_______________________________________________
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®.