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

xen-devel

[Xen-devel] C-state detection (on Intel "Conroe", but possibly generic)

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] C-state detection (on Intel "Conroe", but possibly generic)
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Thu, 27 May 2010 09:44:13 -0700 (PDT)
Delivery-date: Thu, 27 May 2010 09:48:07 -0700
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
I have a Core 2 Duo "Conroe" box, and I just found and disabled
C2 support.  Output of the 'c' debug key is as follows:

(XEN) 'c' pressed -> printing ACPI Cx structures
(XEN) ==cpu0==
(XEN) active state:             C1
(XEN) max_cstate:               C7
(XEN) states:
(XEN)    *C1:   type[C1] latency[000] usage[00028463] duration[96334186317]
(XEN)     C0:   usage[00028463] duration[35090775621]
(XEN) ==cpu1==
(XEN) active state:             C1
(XEN) max_cstate:               C7
(XEN) states:
(XEN)    *C1:   type[C1] latency[000] usage[00013740] duration[103068828568]
(XEN)     C0:   usage[00013740] duration[28356147295]

This box is no longer capable of achieving a cstate
greater than 1, but max_cstate is still shown as C7.
This subverts some of the TSC logic, which measures
if the box can go into deep C-states.

I know I can override this with the Xen max_cstate boot
parameter but shouldn't Xen detect that the highest
C-state possible is 1?  (Linux 2.6.34 does.)

Thanks,
Dan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] C-state detection (on Intel "Conroe", but possibly generic), Dan Magenheimer <=