similar to: [PATCH 1] Add cpufreq governors: performance, powersave, userspace

Hi, The default "stop" action for the cpupower service seems to be to set the ondemand governor, but this fails. I can reproduce the issue directly by running cpupower: $ sudo cpupower frequency-set -g ondemand Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? -

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>

On 03/25/2015 03:47 PM, Konrad Rzeszutek Wilk wrote: > On Mon, Mar 16, 2015 at 02:16:13PM +0100, Peter Zijlstra wrote: >> Hi Waiman, >> >> As promised; here is the paravirt stuff I did during the trip to BOS last week. >> >> All the !paravirt patches are more or less the same as before (the only real >> change is the copyright lines in the first patch).

On 03/25/2015 03:47 PM, Konrad Rzeszutek Wilk wrote: > On Mon, Mar 16, 2015 at 02:16:13PM +0100, Peter Zijlstra wrote: >> Hi Waiman, >> >> As promised; here is the paravirt stuff I did during the trip to BOS last week. >> >> All the !paravirt patches are more or less the same as before (the only real >> change is the copyright lines in the first patch).

it seems getting lost, and thus resend. Thanks, Kevin -----Original Message----- From: Tian, Kevin Sent: 2008年7月24日 8:39 To: ''Jan Beulich'' Cc: Liu, Jinsong; Keir Fraser; xen-devel@lists.xensource.com; mark.langsdorf@amd.com Subject: RE: [Xen-devel] cpufreq info propagation >From: Jan Beulich >Sent: 2008年7月23日 18:13 >> >>startup info is viable. But how

Back in c/s 18950 the default cpufreq governor was set to userspace (it had previously been performance). However, since there is no supplied userspace program or script that will change the frequency this is at best a no-op. Worse, on some hardware with some BIOS revisions, this actually sets the CPUs running at their lowest frequency rather than their highest and there is a corresponding

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

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

[I sent this to the RHEL4 list - but maybe someone on this list knows more] I have a number of dual CPU and dual CPU/dual core Opteron systems that are used as compute servers. In an effort to reduce power consumption and reduce heat output, I would like to make use of the PowerNow! capabilities to clock back the CPUs when the machines are idle. These machines are running a 2.6.9-42 RHEL4 kernel

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. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> diff -r b4278beaf354 xen/arch/x86/platform_hypercall.c --- a/xen/arch/x86/platform_hypercall.c

Hi, This has been a problem since the xen-acpi-processor code was added to the kernel source. I wasn''t sure if the problem I was seeing was related to the old version (4.1.2) of Xen that I was using but now I''m on 4.2.0 and it still exists I thought I would check if I have a misconfiguration or if I have discovered a problem. My system is a dual AMD Opteron(tm) Processor

Hello, Using kernel: 2.6.18-92.1.13.el5.centos.plus the cpu throttling works as desired (see 2 traces below) ------------- trace snips -------------- dmesg | grep -i pow ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0x3fff9b40 powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ processors ( 2 cpu cores) (version 2.20.00) powernow-k8: 0 :

Hi, Is there any documentation on enabling hypervisor support for both C and P-state control? On xen-unstable and linux-2.6.18-xen.hg, if I enable cpuidle=1 on the xen command line and then run xenpm, I will get output for C-states (shown below) but it complains that "Xen cpufreq is not enabled!" cpu id : 0 total C-states : 2 idle time(ms) : 73264 C0

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

I've been playing and comparing frequency scaling between AMD and Intel CPUs yesterday and there seem to be great differences between AMD and Intel and some gotchas. This is all on CentOS 5.2 with latest Xen kernels (which are supposed to be powersaving-enabled since 5.2). AMD: It seems once I get the AMD CPU to use the ondemand governor it works very well and very efficiently. But this

With the third generation Opteron parts, AMD switched to an architecturally defined interface for PowerNow! that uses different MSRs than previous versions. This patch brings the PowerNow! driver up to match the mainline Linux driver and provide support for all AMD parts that use or will use the architectural pstate interface. It also removes a WARN_ON statement in kernel/cpu.c that highlights a

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

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

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

I am seeing random reboots after installing Xen 3.2.1 (running with linux-2.6.18-8 pulled from a few days ago). So far, the reboots only happen if I have enabled cpufreq=dom0-kernel and actually run frequency scaling (such as with the ondemand governor). The reboots only happen after a few hours. The machines seem to be stable if I pass the cpufreq option to Xen but disable frequency scaling. I