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

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

To: Carsten Schiers <carsten@xxxxxxxxxx>
Subject: Re: AW: AW: Re: [Xen-devel] No C-States any longer...
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Wed, 8 Jun 2011 14:56:10 +0100
Cc: "kevin.tian@xxxxxxxxx" <kevin.tian@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "ke.yu@xxxxxxxxx" <ke.yu@xxxxxxxxx>, "yunhong.jiang@xxxxxxxxx" <yunhong.jiang@xxxxxxxxx>
Delivery-date: Wed, 08 Jun 2011 06:56:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <27587646.81307541099106.JavaMail.root@uhura>
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>
Organization: Citrix Systems, Inc.
References: <27587646.81307541099106.JavaMail.root@uhura>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
(reposting my reply to your private mail with the same contentx, I
didn't notice it was private in time, also re-adding CCs to keep
everything on the same thread)

> On Wed, 2011-06-08 at 14:51 +0100, Carsten Schiers wrote:
> Isn't it rather in xen/arch/x86/acpi/cpu_idle.c? I ask because a xm debug-key 
> "c" 
> doesn't print anything, but C-States should be recognized and managed by xen 
> and 
> not by the Dom0 kernel, shouldn't it?

This is outside my comfort zone but AIUI dom0 is responsible for parsing
the ACPI tables and pushing this info down to the hypervisor.

> I found a line like this in function set_cx_pminfo by the way:
> 
> /* FIXME: C-state dependency is nut supported by far */


I think that's just about complex interactions between C states not
being handled, rather than C states not being supported at all.

Ian.

> 
> But maybe it's the same Intel crew that has done it...
> 
> BR,
> Carsten.
> 
> ----- Originalnachricht -----
> Von: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
> Gesendet: Mit, 8.6.2011 11:20
> An: Carsten Schiers <carsten@xxxxxxxxxx>
> Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> ; yunhong.jiang@xxxxxxxxx ; 
> kevin.tian@xxxxxxxxx ; ke.yu@xxxxxxxxx
> Betreff: Re: AW: Re: [Xen-devel] No C-States any longer...
> 
> I'm really not sure how this stuff is supposed to work.
> 
> I've CC'd some Intel folks who authored/touched
> driver/acpi/processor_xen.c and drivers/xen/acpi_processor.c which I
> think is the glue which is supposed to make this stuff work.
> 
> Ian.
> 
> On Tue, 2011-06-07 at 21:16 +0100, Carsten Schiers wrote:
> > I tested with Xen 4.1.0 and latest xen.git#xen/stable-2.6.32: still not 
> > working.
> > Find attached some files. I currently have no working system to produce 
> > equivalents.
> > 
> > BR,
> > Carsten.
> > 
> > -----Ursprüngliche Nachricht-----
> > Von: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx] 
> > Gesendet: Montag, 6. Juni 2011 10:31
> > An: Carsten Schiers
> > Cc: xen-devel
> > Betreff: Re: [Xen-devel] No C-States any longer...
> > 
> > On Sat, 2011-06-04 at 17:18 +0100, Carsten Schiers wrote:
> > > after my move to Xen 4.1.0 and Debian 2.6.32-5-xen-amd64 pvops Dom0. 
> > > Seems to be a problem with ACPI.
> > > Can it be a BIOS problem (although it worked up to now) or is this not 
> > 
> > > implemented? 
> > 
> > It may not have been implemented when Debian took their snapshot of
> > pvops for the Squeeze release or there may have been missing bugfixes.
> > Can you try the latest xen.git#xen/stable-2.6.32?
> > 
> > > Some infos:
> > 
> > It might be interesting to see the equivalent on a working system. Also
> > a complete dmesg from each case would be useful.
> > 
> > Ian.
> > 
> > > 
> > > xm dmesg after xm debug-key c:
> > > --------------------------------
> > > (XEN) 'c' pressed -> printing ACPI Cx structures
> > > 
> > > xenpm get-cpuidle-states 0
> > > --------------------------
> > > Max C-state: C7
> > > 
> > > cpu id               : 0
> > > total C-states       : 0
> > > idle time(ms)        : 0
> > > pc3                  : [00000000000000000018 ms]
> > > pc6                  : [00000000000000004294 ms]
> > > pc7                  : [00000000000140733193 ms]
> > > cc3                  : [00000000000000000000 ms]
> > > cc6                  : [00000000000000000006 ms]
> > > 
> > > xm info
> > > -------
> > > host                   : data
> > > release                : 2.6.32-5-xen-amd64
> > > version                : #1 SMP Thu May 19 01:16:47 UTC 2011
> > > machine                : x86_64
> > > nr_cpus                : 3
> > > nr_nodes               : 1
> > > cores_per_socket       : 3
> > > threads_per_core       : 1
> > > cpu_mhz                : 2210
> > > hw_caps                : 
> > > 
> > 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000
> > > virt_caps              : hvm
> > > total_memory           : 4094
> > > free_memory            : 373
> > > free_cpus              : 0
> > > xen_major              : 4
> > > xen_minor              : 1
> > > xen_extra              : .0
> > > xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
> > 
> > > hvm-3.0-x86_32p hvm-3.0-x86_64
> > > xen_scheduler          : credit
> > > xen_pagesize           : 4096
> > > platform_params        : virt_start=0xffff800000000000
> > > xen_changeset          : unavailable
> > > xen_commandline        : dom0_mem=256M dom0_vcpus_pin cpuidle 
> > > cpufreq=xen
> > > cc_compiler            : gcc version 4.4.5 (Debian 4.4.5-8)
> > > cc_compile_by          : root
> > > cc_compile_domain      :
> > > cc_compile_date        : Fri Jun  3 17:03:43 CEST 2011
> > > xend_config_format     : 4
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > 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



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

<Prev in Thread] Current Thread [Next in Thread>