similar to: [PATCH] x86/cpufreq: check array index before use

struct cpufreq_policy, including a cpumask_t member, gets copied in cpufreq_limit_change(), cpufreq_add_cpu(), set_cpufreq_gov(), and set_cpufreq_para(). Make the member a cpumask_var_t, thus reducing the amount of data needing copying (particularly with large NR_CPUS). Signed-off-by: Jan Beulich <jbeulich@suse.com> --- 2011-09-20.orig/xen/arch/x86/acpi/cpufreq/cpufreq.c 2011-10-12

This fixes an actual bug (failure to exit from a function after an allocation failure), an inconsistency (not removing the cpufreq_dom list member upon failure), and a latent bug (not clearing the current governor upon governor initialization failure when there was no old one; latent because the only current code path leading to this situation frees the policy upon failure and hence the governor

Currently cpufreq and xenpm are out of sync. Fix cpufreq reporting of if turbo mode is enabled or not. Fix xenpm to not decode for tristate, but a boolean. Signed-off-by: Jacob Shin <jacob.shin@amd.com> --- tools/misc/xenpm.c | 14 +++----------- xen/drivers/cpufreq/utility.c | 2 +- 2 files changed, 4 insertions(+), 12 deletions(-) diff --git a/tools/misc/xenpm.c

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1321356497 0 # Node ID 3cfb8f2c4ce898414279d7162206be812584bd5b # Parent 955a6c07dc5e9c55316d1678b2b7cc4313f4fd57 xen: avoid crash enabling turbo mode On a system which has not had P-state information pushed down into the hypervisor running "xenpm enable-turbo-mode" will reliably crash the host. (XEN) PM

Currently, enable/disable turbo mode on AMD is broken: $ xenpm enable-turbo-mode 0 <-- works and proper CPU MSR bit is set $ xenpm enable-turbo-mode 1 <-- silently broken, MSR bit not set Since ->turbo is per policy, when user requests to enable/disable turbo mode, we need to set the bit in all of the ->cpus that this policy affects. --- xen/arch/x86/acpi/cpufreq/powernow.c | 2

Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2008-09-19/xen/arch/x86/platform_hypercall.c =================================================================== --- 2008-09-19.orig/xen/arch/x86/platform_hypercall.c 2008-09-19 14:12:02.000000000 +0200 +++ 2008-09-19/xen/arch/x86/platform_hypercall.c 2008-09-19 14:12:56.000000000 +0200 @@ -21,7 +21,7 @@ #include <xen/acpi.h>

Modify the cpufreq ondemand governor so that it can get idle and total nsecs from the Xen hypervisor.  Xen uses nsecs to measure idle time, while Linux uses ticks. Other than accounting for that difference, use the same algorithm to calculate idle time as Linux does. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> diff -r 26962454b508 drivers/cpufreq/cpufreq_ondemand.c ---

Enable cpufreq support in Xen for AMD Operton processors by: 1) Allowing the PowerNow! driver in dom0 to write to the PowerNow! MSRs. 2) Adding the cpufreq notifier chain to time-xen.c in dom0. On a frequency change, a platform hypercall is performed to scale the frequency multiplier in the hypervisor. 3) Adding a platform hypercall to the hypervisor the scale the frequency multiplier and reset

Currently xen-unstable.hg is broken on ia64 and it should be fixed by Yu''s patch. However he is off this week, so I''m sending the workaround patch. [IA64] Compilation fix to cpufreq stuff. This patch fixes the following compilation error by defining stubs. This patch is just band aid patch until those functions are implemented later. > .../xen/drivers/built_in.o: In

Dear all, The cpufreq modules have been distributed in Centos. But recently, I met a problem when I tried to test the power-related applications. The module can not be modprobed in kernel notwithstanding releated with Centos distribution. The messgae thrown out is: ------------- dump of screen ------------ # modprobe p4-clockmod.ko FATAL: Module p4_clockmod.ko not found

.. snip.. >> Both of them (acpi-cpufreq.c and powernow-k8.c) have a symbol >> dependency on drivers/acpi/processor.c > > But them being ''m'' or ''y'' shouldn''t matter in the end. I thought you were saying it matters - as it should be done around the same time as cpufreq drivers were loaded? .. snip.. >> For a), this would mean some

Hi, I am trying to use the cpufreq driver and was unable to find the same on my xen kernel. I am currently running the folloing kernel: # uname -a Linux mbr-Dom0-3 2.6.18.8-xen #1 SMP Wed Jan 28 10:27:04 IST 2009 x86_64 x86_64 x86_64 GNU/Linux I read in certain places that some versions of Xen donot support cpufreq. But the information was not too clear. Could someone kindly tell me if cpufreq

Some versions of GCC are too stupid to figure out that cpufreq_dom is only used if !!domexist and always set in that case, and complain that it may be used uninitialised. (In general it is IMO better to avoid these kind of flag variables; I would prefer structures like for (...) { cpufreq_dom = dom; if (...) goto cpufreq_dom_found; } cpufreq_dom = 0; cpufreq_dom_found: but on

Hello, I want to use DVFS in xen. I use Fedora 8. The server supports DVFS when it boots from Fedora 8 without xen. Then, I installed Xen 3.4 from source and boots successfully. But the cpufreq directory is gone in the system. I cannnot use DVFS. If I run xenpm get-cpufreq-xxx, it always reports "failed to get xxx". I have googled a lot, but still cannot find the solution. The CPU is

With my OQO, I get the following message when I try to suspend: cpufreq: suspend failed to assert current frequency is what timing core thinks it is. I see in /var/log/messages: kernel: acpi-cpufreq: CPU0 - ACPI performance management activated There are a number of apps and such dedicated to 'cpufreq' on the system. I have done a bit of searching and have not figured out what to do

Hi all :) I''ve been using a tc setup for almost two years, but at some point (probably when I switched to kernel 2.6.x, but I''m not sure) it has started making something very weird. For a certain class, the rate is 125000bit and the ceil is 270000bit, but the fastest rate I get is about 75-80000bit, instead of the "promised" 125000, *with no other traffic in

BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; } Dear All, I was trying to set up a virtual network with fc7 Dom0 and ubuntu 8 (Hardy) & Fedora 9 (etc) as DomU images on AMD Opetron 152 processor based machine. I was able to successfuly establish a virtual network using bridge connection Xen Network configuration. After that I tried to install cpufreq-utils on Dom0 which

Cpufreq domain structure update from array to link list Current cpufreq domain is an array cpufreq_dom_map[NR_CPUS]. However, according to Jan Beulich''s suggestion, domain number may be sparse or bigger than NR_CPUS. This patch update cpufreq domain structure from array to link list, adapt sparse or big domain number. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com>

Set userspace governor as default, which stays same effect as when cpufreq in xen is not enabled. As a result, enable cpufreq in xen by default to avoid reboot to activate cpufreq. Now it''s always on but w/o performance impact if user doesn''t tempt to change governor. We also add some warning info for debug. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com>

I''m using the cpufreq=dom0-kernel hypervisor kernel parameter to enable frequency scaling on the host machines for quite some time now. Since then I started to get the "Time went backwards" message on AMD machines (not on Intel machines). It''s not a big problem, so I only research it once in a while when I stumble upon it from yet another direction. There''s