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] use per-cpu variables in cpufreq

To: 'Juergen Gross' <juergen.gross@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] use per-cpu variables in cpufreq
From: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
Date: Fri, 10 Jun 2011 14:00:26 -0500
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Fri, 10 Jun 2011 12:05:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <eb601128d89304960076.1306494680@nehalem1>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <eb601128d89304960076.1306494680@nehalem1>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwcbfnBHQpERGPDT1mwvIO+YlOHBgLMpx+A
Thread-topic: [Xen-devel] [PATCH] use per-cpu variables in cpufreq
After Keir's comments downthread, are we going to see a 
fresh patch for review?

--Mark Langsdorf
Operating System Research Center
AMD

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Juergen Gross
> Sent: Friday, May 27, 2011 6:11 AM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] [PATCH] use per-cpu variables in cpufreq
> 
> The cpufreq driver used some local arrays indexed by cpu 
> number. This patch
> replaces those arrays by per-cpu variables. The AMD and INTEL 
> specific parts
> used different per-cpu data structures with nearly identical 
> semantics.
> Fold the two structures into one by adding a generic 
> architecture data item.
> 
> Signed-off-by: juergen.gross@xxxxxxxxxxxxxx
> 
> 
> 8 files changed, 58 insertions(+), 66 deletions(-)
> xen/arch/x86/acpi/cpufreq/cpufreq.c       |   36 
> ++++++++++++------------
> xen/arch/x86/acpi/cpufreq/powernow.c      |   43 
> +++++++++++------------------
> xen/drivers/acpi/pmstat.c                 |    6 ++--
> xen/drivers/cpufreq/cpufreq.c             |   24 ++++++++--------
> xen/drivers/cpufreq/cpufreq_ondemand.c    |    2 -
> xen/drivers/cpufreq/utility.c             |    8 ++---
> xen/include/acpi/cpufreq/cpufreq.h        |    3 +-
> xen/include/acpi/cpufreq/processor_perf.h |    2 -
> 
> 
> 

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

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