From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Schiers Subject: AW: AMD P-States not recognized for Xen 3.3 and 3.4 Date: Wed, 7 Jan 2009 11:49:40 +0100 Message-ID: <22664272.161231325380092.JavaMail.root@uhura> References: <49649595.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: In-Reply-To: <49649595.76E4.0078.0@novell.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > ... but was told that it is intentional that there's no code to handle these. Hm. And for what reason it does work in dom0-kernel? Because it's done by powernow-k8.ko and userspace software? ----- Originalnachricht ----- Von: Jan Beulich Gesendet: Mit, 7.1.2009 11:44 An: Carsten Schiers Cc: xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] AMD P-States not recognized for Xen 3.3 and 3.4 >>> Carsten Schiers 07.01.09 10:35 >>> >Xen doesn't seem to fully recognize P-States in my AMD 4050e / Gigabyte M56S-S3 >setting. > >What works is a Xen 3.2-1 Debian with waldi 2.6.18-3.1-2 kernel in a way, that >when specifying cpufreq=dom0-kernel and using cpufreq-set, I can change CPU >frequency (minor problem here: it will report backwards running clocks as mentioned >elsewere here: Timer ISR/0: Time went backwards). > >But using cpufreq=xen will not report any P-states at all. Tried with different >3.3 versions up to 3.3.1 and 3.4 unstable. With cpuidle and without, also did >an update to BIOS F4 (latest version). Used xenpm from 3.3 and 3.4 to check. > >I attached two dmesg / xm dmesg outputs, V1 will show with cpuidle on F4e BIOS, >V2 will show without cpuidle on F4 BIOS. Both used latest Xen 3.4-unstable and >waldi 2.6.18-3.3-1 kernel. > >Any ideas how to proceed? This is a pre-Fam10 CPU you use - I wondered about the lack of support for P-states there as well a while ago, but was told that it is intentional that there's no code to handle these. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel