similar to: Missing /sys/devices/system/cpu/cpu0/cpufreq

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

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

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

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

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

# 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

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

Hi everyone: Just a follow up on the fast clock issue: "Can you double-check that 'cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq' outputs the same number as your 'cpuKHZ' setting in your config.ini file?" There is no cpufreq directory under /sys/devices/system/cpu/cpu0; all I see is "cache" (dir), "crash_notes" (a file) and

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

# 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

The quilt patch titled Subject: cpufreq: powerpc: add missing MODULE_DESCRIPTION() macros has been removed from the -mm tree. Its filename was cpufreq-powerpc-add-missing-module_description-macros.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Jeff Johnson <quic_jjohnson at

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

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

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

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

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

... rather than after. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- 2010-06-15.orig/xen/arch/x86/acpi/cpufreq/cpufreq.c 2010-07-06 16:08:59.000000000 +0200 +++ 2010-06-15/xen/arch/x86/acpi/cpufreq/cpufreq.c 2010-07-06 16:11:48.000000000 +0200 @@ -210,9 +210,11 @@ static u32 get_cur_val(cpumask_t mask) if (!cpu_isset(cpu, mask)) cpu = first_cpu(mask); - policy =

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