[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: RE: [Xen-devel] No C-States any longer...

  • To: Carsten Schiers <carsten@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 9 Jun 2011 12:19:20 +0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc:
  • Delivery-date: Wed, 08 Jun 2011 21:20:00 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcwmWmrBdy5hC8nVRke0B3bayAmT+QAAbU2A
  • Thread-topic: RE: [Xen-devel] No C-States any longer...

> From: Carsten Schiers [mailto:carsten@xxxxxxxxxx]
> Sent: Thursday, June 09, 2011 12:05 PM
> > to verify BIOS problem, you could run a native Linux to verify.
> I can tell you that it worked with the old Xenified 2.6.18 kernel.

Then possibly some patches get lost in your current env...

> > This looks strange. At least C1 should be available. You may check
> Xen/dom0
> > log to see any error there, or manually add some printk in
> set_cx_pminfo to
> > see any error there.
> I check tonight. Does it make sense also to turn debug info on for Dom0
> acpi?

You can have a try though I don't think that gives much hint because
basic ACPI logic doesn't change in Dom0. The more interesting thing is
about the gear logic between dom0 and Xen. Does the dom0 notify
Xen on earth? Is there some condition making Xen reject the call? ...


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.