From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: davej@redhat.com, cpufreq@vger.kernel.org,
linux-kernel@vger.kernel.org, JBeulich@suse.com
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH 2/2] xen/cpufreq: Disable the cpu frequency scaling drivers from loading.
Date: Tue, 13 Mar 2012 19:18:40 -0400 [thread overview]
Message-ID: <1331680720-18268-3-git-send-email-konrad.wilk@oracle.com> (raw)
In-Reply-To: <1331680720-18268-1-git-send-email-konrad.wilk@oracle.com>
By using the functionality provided by "[CPUFREQ]: provide
disable_cpuidle() function to disable the API."
Under the Xen hypervisor we do not want the initial domain to exercise
the cpufreq scaling drivers. This is b/c the Xen hypervisor is
in charge of doing this as well and we can end up with both the
Linux kernel and the hypervisor trying to change the P-states
leading to weird performance issues.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
arch/x86/xen/setup.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index e03c636..4461e0a 100644
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -420,6 +420,7 @@ void __init xen_arch_setup(void)
boot_cpu_data.hlt_works_ok = 1;
#endif
disable_cpuidle();
+ disable_cpufreq();
boot_option_idle_override = IDLE_HALT;
WARN_ON(set_pm_idle_to_default());
fiddle_vdso();
--
1.7.9.48.g85da4d
next prev parent reply other threads:[~2012-03-13 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 23:18 [PATCH] mechanism to disable built in cpu frequency drivers/governors. (v1) Konrad Rzeszutek Wilk
2012-03-13 23:18 ` [PATCH 1/2] [CPUFREQ]: provide disable_cpufreq() function to disable the API Konrad Rzeszutek Wilk
2012-03-14 14:25 ` Dave Jones
2012-03-14 16:26 ` Konrad Rzeszutek Wilk
2012-03-13 23:18 ` Konrad Rzeszutek Wilk [this message]
2012-03-14 7:46 ` [PATCH] mechanism to disable built in cpu frequency drivers/governors. (v1) Jan Beulich
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=1331680720-18268-3-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®