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


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

To: "kevin.tian" <kevin.tian@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: AW: RE: RE: [Xen-devel] No C-States any longer...
From: "Carsten Schiers" <carsten@xxxxxxxxxx>
Date: Thu, 9 Jun 2011 21:08:47 +0200
Delivery-date: Thu, 09 Jun 2011 12:09:44 -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=XY qo8UU0/CDyrpmuat+jAnEwp7K1sVPpGSwDlYEqzy0=; b=uAP+itjYV9BdreuImd 3n7IqS8hUgRYKRAs6D7VtE8HwQ997s8YvsMRkjpMzr2HswXqvF0lAQnRnnNXrLQ2 hbcKQva4q3XneWkoVSzwbusZWl5Y/7AJxeujnBjCKtNUPaA9S5eB5Ce1V45OuKct tZS6OlVs76n6s0rI0ivDumi7c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <625BA99ED14B2D499DC4E29D8138F1505CC5AF722F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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
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.


-----Ursprüngliche Nachricht-----
Von: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
Gesendet: Donnerstag, 9. Juni 2011 06:19
An: Carsten Schiers; xen-devel
Betreff: RE: RE: [Xen-devel] No C-States any longer...

> From: Carsten Schiers [mailto:carsten@xxxxxxxxxx]
> Sent: Thursday, June 09, 2011 12:05 PM
> > to verify BIOS problem, you could run a native Linux to verify.
> I can tell you that it worked with the old Xenified 2.6.18 kernel.

Then possibly some patches get lost in your current env...

> > This looks strange. At least C1 should be available. You may check
> Xen/dom0
> > log to see any error there, or manually add some printk in
> set_cx_pminfo to
> > see any error there.
> I check tonight. Does it make sense also to turn debug info on for 
> acpi?

You can have a try though I don't think that gives much hint because
basic ACPI logic doesn't change in Dom0. The more interesting thing is
about the gear logic between dom0 and Xen. Does the dom0 notify
Xen on earth? Is there some condition making Xen reject the call? ...


Xen-devel mailing list

Xen-devel mailing list