WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

[Xen-devel] AMD P-States not recognized for Xen 3.3 and 3.4

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] AMD P-States not recognized for Xen 3.3 and 3.4
From: Carsten Schiers <carsten@xxxxxxxxxx>
Date: Wed, 7 Jan 2009 10:35:37 +0100
Delivery-date: 2009年1月07日 01:36:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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?

Attachment: dmesg1.txt
Description: Text document

Attachment: dmesg2.txt
Description: Text document

Attachment: xmdemesg2.txt
Description: Text document

Attachment: xmdmesg1.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: RE: [Xen-devel] TPR write optimization (even improves 2003 sp2) , James Harper
Next by Date: [Xen-devel] hvm_set_callback_irq_level() deadlock? , Akio Takebe
Previous by Thread: [Xen-devel] xentrace and MSR_READ/MSR_WRITE , James Harper
Next by Thread: Re: [Xen-devel] AMD P-States not recognized for Xen 3.3 and 3.4 , Jan Beulich
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /