similar to: [PATCH] cpufreq.c: shut up compiler about cpufreq_dom

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

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

# HG changeset patch # User Boris Ostrovsky <boris.ostrovsky@amd.com> # Date 1345135101 -7200 # Node ID 85190245a94d9945b7656c971ba36f7d1eff5c19 # Parent 6d56e31fe1e1dc793379d662a36ff1731760eb0c AMD, powernow: Update P-state directly when _PSD''s CoordType is DOMAIN_COORD_TYPE_HW_ALL When _PSD''s CoordType is DOMAIN_COORD_TYPE_HW_ALL (i.e. shared_type is

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

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

Modify the cpufreq ondemand governor so that it can get idle and total ticks from the Xen hypervisor. Linux and Xen have different ideas of what an idle tick is, so the Xen values for both have to be returned in the same platform hypercall. Otherwise, use basically the same scheme as native Linux. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> iff -r 9bf1ddd0f6bf

.. 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

Another bundle of issues from Coverity triage. The first one is in x86/mm, and looks scarier than it is. The others are all in xen/drivers and AFAICT are pretty minor. Cheers, Tim.

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 ---

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

Enable THERM_CONTROL MSR write for dom0 even cpufreq=xen Signed-off-by: Wei Gang <gang.wei@intel.com> diff -r bd683e0397b4 xen/arch/x86/traps.c --- a/xen/arch/x86/traps.c Tue Feb 17 22:29:38 2009 +0800 +++ b/xen/arch/x86/traps.c Wed Feb 25 11:23:01 2009 +0800 @@ -2187,10 +2187,17 @@ static int emulate_privileged_op(struct case MSR_IA32_MPERF: case MSR_IA32_APERF:

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

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

Hello ! Does anybody know how to build and use cpufreq support that should be in 3.2 since -unstable time ? Bye -- __________________________________________________ Ralf Schenk fon (02 41) 9 91 21-0 fax (02 41) 9 91 21-59 rs@databay.de Databay AG Hüttenstraße 7 D-52068 Aachen www.databay.de Vorstand: Jens Conze, Ralf Schenk, Aresch Yavari Aufsichtsratvorsitzender: Ansgar Vögeli

Hello, I''ve tried to get the CPUFreq plugin of collectd running in dom0. But I mentioned that it isn''t so easy to get a file in sysfs on the rigth place. I know that the value has to come from hypervisor and I''ve seen the code in xenpm. The only value I need is "/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq" which would create cpufreq.c. Can anyone

Hi all :) I''ve tested this and having a cpufreq that slows down the CPU affects the rate of HTB. My ondemand cpufreq governor scales down the CPU frequency about 40% and this is more or less the slowdown the rate suffers, 40%. Any known way of dealing with this without having to disable cpufreq? Thanks in advance :) Ra?l N??ez de Arenas Coronado -- Linux Registered

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

Hi all, I was wondering if cpu frequency scaling in dom0 (using the cpufreq=dom0-kernel boot parameter) may cause problems with HVM domUs? This is on Xen 3.2.1. PV domUs seem to work just fine. They adjust to the frequency change on the go. The HVM I run using the unmodified_driver drivers (also from the 3.2.1 release) seem to have very slow timers if dom0 lowers the frequency. Birger

Could anyone summarize what the support status of cpu frequency changes is at present. I don''t seem to recall generic changes to the hpyervisor in that respect, but the linux tree has fairly extensive changes to the powernow-k8 driver (which would make sense to me only if all other cpufreq drivers are fully supported now, too). Thanks, Jan