From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] use per-cpu variables in cpufreq
Date: Tue, 14 Jun 2011 11:04:02 +0200 [thread overview]
Message-ID: <4DF72402.3060902@ts.fujitsu.com> (raw)
In-Reply-To: <C872CBF75AC4BE4093DF425DEA49BA080A172F4999@sausexmbp02.amd.com>
On 06/10/11 21:00, Langsdorf, Mark wrote:
> After Keir's comments downthread, are we going to see a
> fresh patch for review?
Yes, I think I'll have some time this week to do this.
Sorry for the delay...
Juergen
> --Mark Langsdorf
> Operating System Research Center
> AMD
>
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
>> Juergen Gross
>> Sent: Friday, May 27, 2011 6:11 AM
>> To: xen-devel@lists.xensource.com
>> 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@ts.fujitsu.com
>>
>>
>> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
prev parent reply other threads:[~2011-06-14 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 11:11 [PATCH] use per-cpu variables in cpufreq Juergen Gross
2011-05-27 13:11 ` Keir Fraser
2011-05-27 13:29 ` Juergen Gross
2011-05-28 7:52 ` Keir Fraser
2011-05-30 5:47 ` Juergen Gross
2011-05-30 9:45 ` Keir Fraser
2011-05-31 1:51 ` Tian, Kevin
2011-05-31 7:31 ` Keir Fraser
2011-05-31 7:37 ` Liu, Jinsong
2011-05-30 8:06 ` Tian, Kevin
2011-05-30 15:33 ` Liu, Jinsong
2011-06-10 19:00 ` Langsdorf, Mark
2011-06-14 9:04 ` Juergen Gross [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF72402.3060902@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=mark.langsdorf@amd.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).