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: RE: RE: RE: RE: RE: [Xen-devel] No C-States any longer...

To: Carsten Schiers <carsten@xxxxxxxxxx>
Subject: Re: RE: RE: RE: RE: RE: [Xen-devel] No C-States any longer...
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 15 Jun 2011 12:22:41 -0400
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>
Delivery-date: Wed, 15 Jun 2011 09:23:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110615130638.GD5512@xxxxxxxxxxxx>
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>
References: <5531913.201308128638769.JavaMail.root@uhura> <20110615130638.GD5512@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Jun 15, 2011 at 09:06:38AM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Jun 15, 2011 at 11:03:58AM +0200, Carsten Schiers wrote:
> > Thanks for your support. 
> > 
> > So the plan is to run the very kernel ( from Jeremy's git) 
> > natively, without Xen, and check 
> > what acpi.debug and my printks are reporting?
> > 
> > Would the other check be to change pr_id from -1 to 0 by some helper code 
> > in the right place?
> > 
> > Have I correctly understood that my BIOS seems to implement C-States 
> > through FADT instead of _CST, 
> > which is ok generally, but the FADT PBLK is not correctly set (maybe 
> > because it worries about the -1)?
> So the FADT PBLK is about this line:
>             Processor (CP00, 0x10, 0x00000410, 0x06)
> in your DSDT. The 0x0000410 is the PBLK and somehow it is NULL on your box. 
> You could
> run iasl -d on the DSDT to find out what exactly is there.
> But I *think* that should not affect the C-states as it is just used for 
> reserving some
> CardBus regions.

Or maybe not:http://www.coreboot.org/ACPI

Xen-devel mailing list