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/
Home Products Support Community News


[Xen-changelog] [xen-unstable] Change default cpufreq governor to ondema

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] [xen-unstable] Change default cpufreq governor to ondemand
From: Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 18 Jan 2010 02:50:26 -0800
Delivery-date: Mon, 18 Jan 2010 02:50:59 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1263751630 0
# Node ID 757359a367856bb79b26119292be013a23234c16
# Parent  ff2d29e6ab9cc37e7785fc1758fa9c4b565356d5
Change default cpufreq governor to ondemand

Back in c/s 18950 the default cpufreq governor was set to userspace
(it had previously been performance).  However, since there is no
supplied userspace program or script that will change the frequency
this is at best a no-op.  Worse, on some hardware with some BIOS
revisions, this actually sets the CPUs running at their lowest
frequency rather than their highest and there is a corresponding (and
initially puzzling) drop in performance.

This patch changes the default governor to "ondemand" which should
make it the same as the Linux default and will provide power savings
for the majority without needing to write a userspace governor.  For
those that want to install their own governor, that is still possible.

Signed-off-by: John Haxby <john.haxby@xxxxxxxxxx>
 xen/include/acpi/cpufreq/cpufreq.h |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -r ff2d29e6ab9c -r 757359a36785 xen/include/acpi/cpufreq/cpufreq.h
--- a/xen/include/acpi/cpufreq/cpufreq.h        Sun Jan 17 18:05:32 2010 +0000
+++ b/xen/include/acpi/cpufreq/cpufreq.h        Sun Jan 17 18:07:10 2010 +0000
@@ -100,7 +100,7 @@ extern int cpufreq_register_governor(str
 extern int cpufreq_register_governor(struct cpufreq_governor *governor);
 extern int cpufreq_unregister_governor(struct cpufreq_governor *governor);
 extern struct cpufreq_governor *__find_governor(const char *governor);
-#define CPUFREQ_DEFAULT_GOVERNOR &cpufreq_gov_userspace
+#define CPUFREQ_DEFAULT_GOVERNOR &cpufreq_gov_dbs
 /* pass a target to the cpufreq driver */
 extern int __cpufreq_driver_target(struct cpufreq_policy *policy,

Xen-changelog mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] [xen-unstable] Change default cpufreq governor to ondemand, Xen patchbot-unstable <=