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/
Home Products Support Community News


RE: [Xen-devel] Cpufreq on k8 with xen dom0

To: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
Subject: RE: [Xen-devel] Cpufreq on k8 with xen dom0
From: geaaru <geaaru@xxxxxxxxx>
Date: Fri, 28 Sep 2007 16:45:31 +0200
Cc: Xen-Devel ML <xen-devel@xxxxxxxxxxxxxxxxxxx>, Goswin von Brederlow <brederlo@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, Bhavana Nagendra <bnagendr@xxxxxxxxxx>
Delivery-date: Fri, 28 Sep 2007 07:46:55 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:reply-to:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=vzYGPxboXaRkwidj7i8+9oT2C3lXqB1mJmKkhOuo4po=; b=QPLH+PlqmEPzOULtBB+XrnY8lHKQh4Yz4w2R0wL91q1MZVCYgCrmYA8chIkX6M6KYJ3WT1JdObI36g+rQ5d6RBH1k9DbnZg/J+HcSjtzocVmA80JNmrMiQ3m1SbyzpjCg1iIOWN5X65r9KFinKXMguwXC/YmU/GO7cbtdJD/RG8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:reply-to:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=VyEbq0Z0iTfeNlfxCOn1sVh7BlqZmR+fZXINn8o1EBa34/JmtZz7bL/rUruIwKJmHdfzmZ4v5E5+bnZCqjUryh4iIzvkncy0rw+3n5EaIBn7HR+D1yhev5EnGdlsCmcndyzuuA5a4W01f9Az70qjEKXikTdis/0PQAKyDj5uMvQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1449F58C868D8D4E9C72945771150BDF02077034@xxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1190726705.9986.18.camel@localhost> <1449F58C868D8D4E9C72945771150BDF0207701C@xxxxxxxxxxxxxxxxx> <87tzpg63p0.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1449F58C868D8D4E9C72945771150BDF0207702E@xxxxxxxxxxxxxxxxx> <1190975833.6909.2.camel@localhost> <1449F58C868D8D4E9C72945771150BDF02077034@xxxxxxxxxxxxxxxxx>
Reply-to: geaaru@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
My current kernel version 2.6.22 (as previous versions 2.6.21, 2.6.20)
native works fine. Probably, there is a difference (as you said me)
between Xen ACPI Interpreter and the native mode interpreter.
I try also with xen-source-2.6.18 tree without xen support and in this
case, cpufreq works fine. Only if i enable xen cpufreq doesn't work.

On Fri, 2007-09-28 at 07:44 -0500, Langsdorf, Mark wrote: 
> > Hi, i try to use xen-unstable.hg version but doesn't work.
> > 
> > >From dmesg i have this error:
> > 
> > powernow-k8: Found 1 AMD Turion(tm) 64 Mobile Technology ML-30
> > processors (version 2.00.00)
> > powernow-k8: BIOS error - no PSB or ACPI _PSS objects
> > ACPI: (supports S0 S3 S4 S5)
> > 
> > While, if i try to call cpufreq-info i have this output:
> > 
> > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > Report errors and bugs to linux@xxxxxxxx, please.
> > analyzing CPU 0:
> >   no or unknown cpufreq driver is active on this CPU
> > 
> > any idea how can i resolve this problem?
> dom0 isn't seeing the ACPI _PSS objects (I thought the
> error message made that clear).  No ACPI objects means
> no information on the pstates.
> Do you get PowerNow! support on a native version 2.6.21+
> kernel?  If not, you need to update your BIOS to something
> that supports pstates (or possibly you have one of the
> rare Turions that doesn't support more than 1 pstate,
> but I doubt that).  
> If 2.6.21+ native works, check to see if 2.6.18 native
> works.  If it doesn't, then there was a change to the
> ACPI interpreter to support your laptop that will need
> to be backported.  If 2.6.18 native works, then there's
> a difference between the Xen ACPI interpreter and the
> native mode interpreter that will need to be ported to
> Xen.
> -Mark Langsdorf
> Operating System Research Center

Xen-devel mailing list