similar to: CPU Freq Scaling

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

Stephen John Smoogen <smooge at gmail.com> writes: > On 1 October 2017 at 11:34, hw <hw at adminart.net> wrote: >> Hi, >> >> is there a way in Centos to find out if the Intel turbo mode will be >> used? >> >> Using the 'stress' utility and checking the frequency with cpupower >> tells me that a CPU is running at it?s maximum

Hi, is there a way in Centos to find out if the Intel turbo mode will be used? Using the 'stress' utility and checking the frequency with cpupower tells me that a CPU is running at it?s maximum frequency as reported by cpupower --- and this frequency is less than the frequency it would run at if it used the turbo mode. All the other CPUs are at their minimum frequency. I have verified

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

Hi all - First the boilerplate: On centos-release.x86_64 7-0.1406.el7.centos.2.3 [root at localhost x86_64]# uname -a Linux localhost.localdomain 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root at localhost x86_64]# rpm -qa kernel\* | sort kernel-3.10.0-123.el7.x86_64 kernel-devel-3.10.0-123.el7.x86_64

Hi, while testing some APERF/MPERF semantics I discovered that this feature is enabled in Xen Dom0, but is not reliable. The Linux kernel''s scheduler uses this feature if it sees the CPUID bit, leading to costly RDMSR traps (a few 100,000s during a kernel compile) and bogus values due to VCPU migration during the measurement. The attached patch explicitly disables this CPU capability

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

On 3 October 2017 at 13:01, hw <hw at adminart.net> wrote: > Stephen John Smoogen <smooge at gmail.com> writes: > >> On 1 October 2017 at 11:34, hw <hw at adminart.net> wrote: >>> Hi, >>> >>> is there a way in Centos to find out if the Intel turbo mode will be >>> used? >>> >>> Using the 'stress' utility

Hello I'm building a router/proxy/firewall, the default governor is ondemand, but for this application, what governor is best suited? (for example conservative?) Thanks at all! Best regards

Hi, i read the xenpm wiki page, but i cannot use the "p-states". xenpm shows: xenpm cpu id : 0 total C-states : 2 idle time(ms) : 1776034 C0 : transition [00000000000000000000] residency [00000000000000000000 ms] C1 : transition [00000000000000260278] residency

On 1 October 2017 at 11:34, hw <hw at adminart.net> wrote: > Hi, > > is there a way in Centos to find out if the Intel turbo mode will be > used? > > Using the 'stress' utility and checking the frequency with cpupower > tells me that a CPU is running at it?s maximum frequency as reported by > cpupower --- and this frequency is less than the frequency it would

Specifically, what values are or aren''t accepted as CPU identifier, and how the values get interpreted should be consistent across sub-commands (intended behavior now: non-negative values are okay, and along with omitting the argument, specifying "all" will also be accepted). For error handling, error messages should get consistently issued to stderr, and the tool should now

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

I have a specific question and a general question. Specific Question: I want to do an analysis on a data frame by 2 or more class variables (i.e., use 2 or more columns in a dataframe to do statistical classing). Coming from SAS, I'm used to being able to take a data set and have the output of the analysis in a dataset for further manipulation. I have a data set with vote totals, with one

Hi I'm using Gluster 3.2.5. After expanding a 2x2 Distributed-Replicate volume to 3x2 and performing a full rebalance fuse clients log the following messages for every directory access: [2012-03-08 10:53:56.953030] I [dht-common.c:524:dht_revalidate_cbk] 1-bfd-dht: mismatching layouts for /linux-3.2.9/tools/power/cpupower/bench [2012-03-08 10:53:56.953065] I

Hi all, I installed Performance Co-Pilot 3 days ago, and installed the nVidia PMDA according to the instructions at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/ch03s03s02.html and was able to view metrics about my video card using pmchart. I then played around a little with the lmsensors PMDA (but it doesn't look too useful to me -

Hey, folks, Sometimes my workstation bogs down... slows to a crawl. Using gkrellm, it's obvious the CPU is the laggard. The top utility confirms: the load average gets up over 4 at times. But this occurs when cpu stepping pegs the speed at 600MHz. This processor is capable of 1.5GHz and when it's allowed to run at that speed, the load average is under 2, which is fine. So the

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

Existing credit scheduler is not power aware. To achieve better power saving ability with negligible performance impact, following areas may be tweaked and listed here for comments first. Goal is not to silly save power with sacrifice of performance, e.g. we don''t want to prevent migration when there''re free cpus with some pending runqueues. But when free computing power is