From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: AMD P-States not recognized for Xen 3.3 and 3.4 Date: Wed, 07 Jan 2009 10:44:21 +0000 Message-ID: <49649595.76E4.0078.0@novell.com> References: <26336541.151231320937178.JavaMail.root@uhura> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <26336541.151231320937178.JavaMail.root@uhura> 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: Carsten Schiers Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> 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=20 >when specifying cpufreq=3Ddom0-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=3Dxen 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