[Xen-devel] [PATCH] use per-cpu variables in cpufreq

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-devel] [PATCH] use per-cpu variables in cpufreq
From:	Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date:	Fri, 27 May 2011 13:11:20 +0200
Delivery-date:	Fri, 27 May 2011 06:01:03 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1306500969; x=1338036969; h=mime-version:subject:message-id:date:from:to; bh=OQ7MwE7hgfa27IPeOVZIYNuXi5j+Jc0Jpa0nIu5ceTg=; b=pnPA/iqnJXe3L+9SiOQ9sdsuyj3zp5ZJnrMPubhs2iLIyIZKKzzCeKHF UvnOrBWjgR0vIZvKV0Nn61y8gQB0dgLwh8BljD9EMVP3oyROmHbqk91Qy XXcqU6nLhDcF+sa4lccetzAj94l7zACcmxbZ4W3hzRMv6XVXClimSZJJt 4lI07hkpgDidwrVRo6gIBtTLuPtFfHZvghmysK+T1z2RbdnlEQfHxhGTQ cpPth/U9CFvKGVJhhSSrfWQWufkDf;
Domainkey-signature:	s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Content-Type:MIME-Version:Subject: X-Mercurial-Node:Message-Id:Date:From:To; b=oS2RwIIwqwDjVoWPQBrZoAvvRIuhoImXWl3r8XHJ4KFSX4QMnjgwIirT xUzXCiOe/TiW+CBkhjqwt/J8MyoIPQqeMyF6yAjVkW8Xlf02BhMCOGBaf +/TU6KoDG//Ewb1Sa8UExLOcJDlhTLdyT7q49jxPMrlf5J/tKPPNnTpuy Difkrxhvxw2CA39AsNmMwx470fQ24sSmtzl2BoSHO18C50SmHt6OwPEVx Xg8QYCYU1PAto1lHxCN0gxEayXe5m;
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

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-work.patch
Description: Text Data

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] [PATCH] use per-cpu variables in cpufreq