From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Schiers Subject: AW: RE: RE: No C-States any longer... Date: Fri, 10 Jun 2011 10:57:00 +0200 Message-ID: <26636845.61307696220036.JavaMail.root@uhura> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" , xen-devel List-Id: xen-devel@lists.xenproject.org I was faster, just build a new acpi_processor.ko that will report with a lot of printks in drivers/acpi/processor_xen drivers/acpi/processor_idle as the stuff from drivers/xen/ simply isn't called. Not able to test it right now, because I don't want to do a remote reboot and find my family anoyed when Internet and TV is not working ;o). I will check this afternoon when I am back from work. Carsten. ----- Originalnachricht ----- Von: "Tian, Kevin" Gesendet: Fre, 10.6.2011 10:48 An: Carsten Schiers ; xen-devel Betreff: RE: RE: RE: [Xen-devel] No C-States any longer... > From: Carsten Schiers [mailto:carsten@schiers.de] > Sent: Friday, June 10, 2011 3:09 AM > > Through some adding of printk I was able at least to verify that for my > 3 core CPU AMD Athlon X3 400e > > - xen_px_notifier is called six times > - Hypervisor is reporting XEN_PM_PX is called six times > - Hypervisor is never reporting XEN_PM_CX to have been called > - this is because xen_cx_notifier is never called. > -> set_cx_pminfo is never called. > > What I will try to find out next is to check where xen_cx_notifier > *should* be called. OS debugging is > not realy my expertise, let's see whether you first can give me a hint > or whether I am quicker to find > it on my own. > the entry point in dom0 looks like: xen_acpi_processor_start xen_acpi_processor_power_init processor_cntl_xen_notify xen_ops.pm_ops xen_cx_notifier HYPERVISOR_dom0_op Thanks Kevin