similar to: cpufreq info propagation

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

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

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

These two patches provide the neccessary infrastructure changes for the processor-passthru driver [www.spinics.net/lists/linux-acpi/msg34655.html] to properly function. The first one is quite easy - we just modprobe the processor-passthru driver. The second allows it to work under AMD machines by exposing the PM RDMSR to dom0. It has been tested with 2.6.32 kernel as well to make sure it does

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

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, I recently subscribed to xen-users asking about a powernow-k8 problem, but in the meantime I am not sure if the users-list was the right place for it. So I decided to repeat my question here ;-) My current config is attached. --- snip --- Hi, I recently installed Xen on my AMD64 for my first time and so far, everything seems to work pretty fine. :-) I tried to enable cpu frequency

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

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

hello, yet another powerd SOS : on an ASUS M3A78-EM MB with Phenom 9750 and 8 gig memory, starting powerd freezes the box after slowing down a bit cpu frequency. [IMHO] usefull bit of info : FreeBSD m34.scito.local 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Thu Dec 11 14:24:39 CET 2008 root@m34.scito.local:/usr/obj/raid1/bsd/src7/sys/M3A78-EM amd64 CPU: AMD Phenom(tm) 9750 Quad-Core

Hi, I''ve recently installed xen-3.2.1 on my AMD Sempron(tm) machine. It runs gentoo 2.6.21 as dom0 and cpu frequency scaling works in dom0. But inside a domU, cpu frequency scaling is not working. By checking the boot log in domU I found that domU is unable to load the powernow driver: "powernow-k8: BIOS error - no PSB or ACPI _PSS objects" I wonder if it is possible to have

Hi; While using xen-3.0.2 with 2.6.16.28 kernel CPU (Intel(R) Pentium(R) M processor 1.73GHz) temprature is inreasing up to 104 C (/proc/acpi/thermal_zone/THRM/trip_points reports 105 C is critical for CPU) while idle or no domU working with very low system load, and if i start to use domU, sometimes system freezes or reboots for heat. But the same kernel just without Xen works normally and

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

Hi, I noticed that the fan of my centrino is very often running since I use Xen (the load is very low still). Also the cpufreq is always at 600MHz (the max is 1500MHz), regardless of what of what heavy computations I do (e.g. calculating md5sums). I heard that it is not possible to run a cpufreq scheduler like powernowd or cpufreqd, but would it be possible to set the cpu frequency at least

Hey all, Since moving a 4.3 x86-64 install from a single athlon64 to a new dual core AMD cpu it would appear that cool'n quiet is having trouble as is shown in the system logs; powernow-k8: ignoring illegal change in lo freq table-2 to 0x2 powernow-k8: transition frequency failed Any ideas ? Cheers, Brian.

Hi I have a compaq R4000 with the 2.4GIG AMD 64 bit. 4000+ rated. proc cpuinfo reports cpu Mhz as 997.481 Do I have to run the 64 bit version to have things run correctly? I just have the normal 4.2 loaded at this time. The laptop seems slow for 4000+ as reflected by the cpu Mhz also. Any thoughts on running the 32 bit version of 4.2 vs the 64 bit version of 4.2? Jerry

Sorry to have so many questions but I seem to have quite a few mini problems with my first Xen setup. My xen server works fine with Powernow on the standard Kernel but with the Xen kernel it fails. Does anyone know why? Details below. With Standard Kernel powernow-k8: Found 2 Quad-Core AMD Opteron(tm) Processor 8350 processors (8 cpu cores) (version 2.20.00) powernow-k8: 0 : fid 0x0

This changeset reverts two previous corrections, for reasons that escape me. First, the domain map is again being confined to NR_CPUS, which I had submitted a patch to fix recently (yes, I realize the code has a TODO in there, but those really get forgotten about far too often). Second, the platform hypercall was reverted back to require all information to be passed to Xen in one chunk, whereas

To my surprise, c/s 8888 enables CPU_FREQ for x86-64 rather than disabling it for i386. Did anyone at your end actually test that if enabled this at least builds properly now? Not to mention that of course this also should work... If I remember right, the main reason for posting a patch to disable it on 32-bits (similar to how it was on 64-bits before) was that there were some missing symbols, and

Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock