xen-devel
RE: RE: RE: RE: RE: RE: [Xen-devel] No C-States any longer...
To: |
Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Carsten Schiers <carsten@xxxxxxxxxx> |
Subject: |
RE: RE: RE: RE: RE: RE: [Xen-devel] No C-States any longer... |
From: |
"Tian, Kevin" <kevin.tian@xxxxxxxxx> |
Date: |
Thu, 16 Jun 2011 10:12:23 +0800 |
Accept-language: |
en-US |
Acceptlanguage: |
en-US |
Cc: |
xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "mark.langsdorf@xxxxxxx" <mark.langsdorf@xxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx> |
Delivery-date: |
Wed, 15 Jun 2011 19:13:44 -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 |
Thread-index: |
AcwrXR1fGXVZcMj2Qt200Vvao4E2HQAbVqkA |
Thread-topic: |
RE: RE: RE: RE: RE: [Xen-devel] No C-States any longer... |
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx]
> Sent: Wednesday, June 15, 2011 9:07 PM
>
> 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 (2.6.32.40 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.
Just a caveat that manual iasl may not match the actual content observed by the
kernel, because OSPM may notify BIOS for its supported capability which then
may further impact final visible content. :-)
Thanks
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|