similar to: [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes

Hello ! Does anybody know how to build and use cpufreq support that should be in 3.2 since -unstable time ? Bye -- __________________________________________________ Ralf Schenk fon (02 41) 9 91 21-0 fax (02 41) 9 91 21-59 rs@databay.de Databay AG Hüttenstraße 7 D-52068 Aachen www.databay.de Vorstand: Jens Conze, Ralf Schenk, Aresch Yavari Aufsichtsratvorsitzender: Ansgar Vögeli

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

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

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

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

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

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

After installing a Phenom II X4 processor (replacing a single core Semperon) I am getting these messages on the console and in dmesg: Warning Timer ISR/2: Time went backwards: delta=-250135996 delta_cpu=13864004 shadow=1355887856733 off=870052783 processed=1357008044419 cpu_processed=1356744044419 0: 1357004044419 1: 1356696044419 2: 1356744044419 3: 1356696044419 printk: 41 messages

It''s everytime when cpufreq_ondemand or cpufreq-set changes the frequency, aprox. 3 messages per event. Is that occasional? I tend to say: no. Please see an excerpt below. And if it''s not occasional, what could I do? And by the way: I found no code that TSC will get adjusted, so I think it will get worse over the time... Thanks, Carsten. messages.0:Jan 9 12:25:15 data kernel:

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

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

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

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

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

Hi all, We recently upgrade from CentOS 5.8 to CentOS 5.9 on kernel-xen-2.6.18-348.3.1.el5, and after booting into the new kernel, noted large amounts of these messages every second or so in the logs: Mar 30 21:38:35 atlas2 kernel: Warning Timer ISR/0: Time went backwards: delta=-1393683849 delta_cpu=22316151 shadow=225003685197135 off=129240997 processed=225005208029053

Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2008-09-19/xen/arch/x86/platform_hypercall.c =================================================================== --- 2008-09-19.orig/xen/arch/x86/platform_hypercall.c 2008-09-19 14:12:02.000000000 +0200 +++ 2008-09-19/xen/arch/x86/platform_hypercall.c 2008-09-19 14:12:56.000000000 +0200 @@ -21,7 +21,7 @@ #include <xen/acpi.h>

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