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


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

To: Carsten Schiers <carsten@xxxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>
Subject: RE: RE: RE: RE: RE: RE: [Xen-devel] No C-States any longer...
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Thu, 16 Jun 2011 10:09:11 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 15 Jun 2011 19:11:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <10635020.231308129129960.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>
References: <10635020.231308129129960.JavaMail.root@uhura>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwrPFJEphIAy5tZTgyxbLrZesrgYQAjbS4A
Thread-topic: RE: RE: RE: RE: RE: [Xen-devel] No C-States any longer...
> From: Carsten Schiers [mailto:carsten@xxxxxxxxxx]
> Sent: Wednesday, June 15, 2011 5:12 PM
> > this looks a bit strange. how about the native log?
> I have not done a log with ACPI_DEBUG enabled. Will do so tonight or
> tomorrow night.
> > what's your dom0 vcpu number? and how about physical cpu?
> dom0_vcpu_pin/xend-config.sxp result in the following excerpt of xm vcpu-list:
>   Name          ID          VCPU          CPU
> State          ...
>   Domain-0      0           0             0
> r--            ...
>   Domain-0      0           1             -
> --p            ...
>   Domain-0      0           2             -
> --p            ...
>   ...
> > there's possibility that in your environment general ACPI code
> > is changed which is not reflected in Xen specific versions.
> I have not understood that.

as you see already, there's some ACPI function duplicated into a Xen specific
version to handle some tricky assumptions, such as 
So it's possible that, if same kernel works well natively, those Xen stubs are 
out of
sync with original version. This is not a clean approach, and we need consider 
a better
one for pushing them upstream. :/


Xen-devel mailing list