aboutsummaryrefslogtreecommitdiffstats
path: root/tools/hotplug
diff options
context:
space:
mode:
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2012-03-23 09:45:56 -0400
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2012-03-23 09:45:56 -0400
commit5d55ddd882498945ac7d33343503a33642e198d9 (patch)
treeed23d6c6fdb1ccc1e03e1a59c7f12b255f174ee3 /tools/hotplug
parentbfed971ab60ac927e22b431565fc9432edc3229a (diff)
downloadxen-5d55ddd882498945ac7d33343503a33642e198d9.tar.gz
xen-5d55ddd882498945ac7d33343503a33642e198d9.tar.bz2
xen-5d55ddd882498945ac7d33343503a33642e198d9.zip
linux-xencommons: Load xen-acpi-processor
Upstream the "xen/acpi-processor: C and P-state driver that uploads said data to hypervisor." takes care of uploading power information information that normally a cpu frequency scaling driver would using in the initial domain. We want the hypervisor to take that data and make good usage of it. Fortunatly for us we do not have to worry about the native cpu frequency scaling drivers being loaded first, as the upstream commit: "xen/cpufreq: Disable the cpu frequency scaling drivers from loading." takes care of that. Meaning we can load the xen-acpi-processor at any time. By default that driver is built as a module - and since we are the only user of it - we should load it. Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Committed-by: Ian Jackson <ian.jackson.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Diffstat (limited to 'tools/hotplug')
-rw-r--r--tools/hotplug/Linux/init.d/xencommons1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/hotplug/Linux/init.d/xencommons b/tools/hotplug/Linux/init.d/xencommons
index 6c72dd81e7..2f81ea2d90 100644
--- a/tools/hotplug/Linux/init.d/xencommons
+++ b/tools/hotplug/Linux/init.d/xencommons
@@ -58,6 +58,7 @@ do_start () {
modprobe xen-gntdev 2>/dev/null
modprobe evtchn 2>/dev/null
modprobe gntdev 2>/dev/null
+ modprobe xen-acpi-processor 2>/dev/null
mkdir -p /var/run/xen
if ! `xenstore-read -s / >/dev/null 2>&1`