[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] How to use deeper C state
The max_cstate just means if there are c-state deep to C7, those deep C states can be entered. But from below debug out, I found the deepest C state supported is C1 in you machine because all supported C states will be printed out. You machine may not support deep C states, or dom0 failed to detected it from BIOS. Can you provide the whole 'xm dmesg' result right after booting up? Jimmy On Wednesday, January 21, 2009 5:03 PM, Akio Takebe wrote: > Hi, > > When I tried cpuidle option, > max_cstate indicates C7 with debug-key in my machine. > But the result of "xenpm start" doesn't say > that xen enter C2 or more state. > Do I need anything else(boot option and so on)? > > > (XEN) ==cpu0== > (XEN) active state: C1 > (XEN) max_cstate: C7 > (XEN) states: > (XEN) *C1: type[C1] latency[000] usage[00409594] duration > [1893990621775] > (XEN) C0: usage[00409594] duration[22279357433] > (XEN) ==cpu1== > (XEN) active state: C1 > (XEN) max_cstate: C7 > (XEN) states: > (XEN) *C1: type[C1] latency[000] usage[00396768] duration > [1891756608514] > (XEN) C0: usage[00396768] duration[24513377367] > > # xenpm start > Elapsed time (ms): 466915 > CPU0: > residency percentage > C0 220 ms 0.05% > C1 466695 ms 99.95% > P0 60 ms 100.00% > P1 0 ms 0.00% > > CPU1: > residency percentage > C0 606 ms 0.13% > C1 466309 ms 99.87% > P0 450 ms 100.00% > P1 0 ms 0.00% > > > Best Regards, > > Akio Takebe > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |