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


[Xen-devel] [PATCH][pvops_dom0][0/4] parse ACPI Cx/Px info for Xen

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] [PATCH][pvops_dom0][0/4] parse ACPI Cx/Px info for Xen
From: "Yu, Ke" <ke.yu@xxxxxxxxx>
Date: Sun, 19 Jul 2009 14:45:12 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 18 Jul 2009 23:45:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
Thread-index: AcoIPHbaAnB7s8xPQG+RbYEHnSP+7Q==
Thread-topic: [PATCH][pvops_dom0][0/4] parse ACPI Cx/Px info for Xen
Xen hypervisor depends on dom0 to parse the physical ACPI Cx/Px information and 
pass the info to xen. The following series of patches implements this 

01/04 domain0-acpi-parser-related-hypercall.patch:      add acpi parser related 
platform hypercall
02/04 external-control-framework.patch:                         Introduce the 
external control operation interface for domain0 ACPI parser
03/04 external-control-xen.patch:                                       Xen 
implementation of the external control operation interface
04/04 xen-vcpu-pcpu-mapping.patch:                              use physical 
acpi_id in acpi processor parsing logic

Note that the 04 patch xen-vcpu-pcpu-mapping.patch is a bit hacky. Its purpose 
is fixing the gap between dom0 vcpu and physical acpi info. but due to that 
this is a the architecture issue, no clean way is found with current 
architecture. There is thread talking about moving the ACPI parser from dom0 to 
hypervisor. this issue will gone under such architecture. But by far, we have 
to use this kind of hacky patch.

Also this series of patches are rebased version of the previous post. Most of 
the comments Jeremy provided last time is applied, with only one exception: use 
xen specific cpufreq driver for the Px info. I tried this approach, and finally 
find this approach need many hacks in cpufreq path to fix the gap of vcpu and 
physical cpu. so I still keep the Px logic in external control logic instead of 
cpufreq driver.

Best Regards

Xen-devel mailing list

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