similar to: cpu frequency scaling in domUs

Hi, Does Xen provide support for CPU frequency scaling? If there exists such support, from which version they support it? Otherwise what problems do exist in support frequency scaling in Xen? Thanks, Vahid _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi! I would like to know the status of the frequency scaling in XEN. I found a web site saying that XEN doesn’t work with frequency scaling, at the other hand I found some fixes for powernow-k8 to get rid of some messages. I have an AMD64. powerno-k8 works find with non-XEN kernels, but with XEN-kernels I get the error: powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3400+ processors

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

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

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

Now that I finally got around to update our sources, I had a closer look at those changes, and apart from stylistic issues on the Linux side (part of which I may have asked for, but the result was somewhat overdone so the code is hardly legible now - I''ve got a patch queued to streamline this a little) I find it rather odd (fragile) that the who-is-in-charge information gets propagated

Hello, The following patches are a solution to a problem we have encountered when using the Xen hypervisor: - Need Pxx/Cxx states to save on power consumption when using Xen (we do want those datacenters to consume less power!), - Also need to figure out the Turbo mode so that the scheduler can properly boost a core for CPU bound guests. In essence the Xen hypervisor requires that

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, I am using Xen 3.2.1 and I cannot boot it on my machine unless I use the noacpi option. As far as I know noacpi option is incompatible with SMP, so I must not use it, because my machine is SMP. I am describing the problem in more detail below. If you could point me in the right direction, I''d greatly appreciate it. I downloaded Xen 3.2.1 official source distribution tarball from

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

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

Hi all! After booting the server I have this message: irq 50: nobody cared (try booting with the "irqpoll" option) Call Trace: <IRQ> [<ffffffff800c17e6>] __report_bad_irq+0x30/0x7d [<ffffffff800c1a19>] note_interrupt+0x1e6/0x227 [<ffffffff800c0f15>] __do_IRQ+0xbd/0x103 [<ffffffff8006e249>] do_IRQ+0x13f/0x14d [<ffffffff8006ca05>]

Does Xen provide support for CPU frequency scaling? If there exists such support, from which version they support it? Otherwise what problems do exist in support frequency scaling in Xen? Thanks, This message posted from opensolaris.org

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 :

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

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

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

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