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

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

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: AW: AW: Re: [Xen-devel] No C-States any longer...
From: Carsten Schiers <carsten@xxxxxxxxxx>
Date: Wed, 8 Jun 2011 15:51:39 +0200
Delivery-date: Wed, 08 Jun 2011 06:53:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=simple; d=mail.zeus06.de; h=date: from:to:message-id:in-reply-to:subject:mime-version: content-type:content-transfer-encoding; q=dns/txt; s=beta; bh=sv kO9qNd0TlF3jznKzNEj66rolbgeMX9Z4k1I363xUA=; b=Pu17tLyBvNpknefEFL 2MDVQT5TwVlNvkSoKPh/T2wWPlyXhHXCsXJrceVKpZhqzwcXR4nFWLJB4hHfphE+ PNBVHryb+m/fw5v15G+x3HmBJ4h+DFIf1FMDFMH8AaFumBSFPEamfLvar7U/CFQx 3JL0kAJdciLEwrP6hQ23bDYhQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <15131694.51307540285845.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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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?

I found a line like this in function set_cx_pminfo by the way:

/* FIXME: C-state dependency is nut supported by far */

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

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