From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, keir.fraser@eu.citrix.com,
Ian.Jackson@eu.citrix.com, Ian.Campbell@citrix.com
Cc: konrad.wilk@oracle.com
Subject: [PATCH 1 of 6] linux-xencommons: Load xen-acpi-processor
Date: Sat, 24 Mar 2012 13:41:42 -0400 [thread overview]
Message-ID: <708bf485e5d4baaf1c62.1332610902@phenom.dumpdata.com> (raw)
In-Reply-To: <patchbomb.1332610901@phenom.dumpdata.com>
# HG changeset patch
# User Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
# Date 1332608051 14400
# Node ID 708bf485e5d4baaf1c6272bd4fb1895a3c355d3e
# Parent b7a1794aed59fd2b0816b3bbcf97690c0241814f
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>
diff -r b7a1794aed59 -r 708bf485e5d4 tools/hotplug/Linux/init.d/xencommons
--- a/tools/hotplug/Linux/init.d/xencommons Fri Mar 23 13:45:28 2012 +0000
+++ b/tools/hotplug/Linux/init.d/xencommons Sat Mar 24 12:54:11 2012 -0400
@@ -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`
next prev parent reply other threads:[~2012-03-24 17:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 17:41 [PATCH 0 of 6] Various patches - debug help, xend fixes and S3 resume fixes (v1) Konrad Rzeszutek Wilk
2012-03-24 17:41 ` Konrad Rzeszutek Wilk [this message]
2012-03-27 13:39 ` [PATCH 1 of 6] linux-xencommons: Load xen-acpi-processor Ian Jackson
2012-03-24 17:41 ` [PATCH 2 of 6] xen/vga: Add 'vga_delay' parameter to delay screen output by 2 second per screen output Konrad Rzeszutek Wilk
2012-03-26 8:43 ` Jan Beulich
2012-03-27 13:41 ` Ian Jackson
2012-03-24 17:41 ` [PATCH 3 of 6] xen/pat: After suspend re-write PAT if BIOS changed it Konrad Rzeszutek Wilk
2012-03-26 8:50 ` Jan Beulich
2012-04-02 15:28 ` Konrad Rzeszutek Wilk
2012-04-03 13:03 ` Tom Goetz
2012-03-24 17:41 ` [PATCH 4 of 6] xend: Don't crash due to weird PCI devices Konrad Rzeszutek Wilk
2012-03-27 13:39 ` Ian Jackson
2012-03-24 17:41 ` [PATCH 5 of 6] xend/xc: Implement a domain_set_e820_hole function to be used by python code Konrad Rzeszutek Wilk
2012-03-26 9:42 ` Ian Campbell
2012-04-02 15:59 ` Konrad Rzeszutek Wilk
2012-04-02 16:02 ` Ian Campbell
2012-03-24 17:41 ` [PATCH 6 of 6] xend: Add support for passing in the host's E820 for PCI passthrough Konrad Rzeszutek Wilk
2012-03-27 13:43 ` Ian Jackson
2012-04-02 16:00 ` Konrad Rzeszutek Wilk
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=708bf485e5d4baaf1c62.1332610902@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.