search for: _cst

Enable Px/Cx related CPUID/MSR bits for dom0 to get correct Px/Cx info. Signed-off-by: Wei Gang <gang.wei@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Enable cpufreq support in Xen for AMD Operton processors by: 1) Allowing the PowerNow! driver in dom0 to write to the PowerNow! MSRs. 2) Adding the cpufreq notifier chain to time-xen.c in dom0. On a frequency change, a platform hypercall is performed to scale the frequency multiplier in the hypervisor. 3) Adding a platform hypercall to the hypervisor the scale the frequency multiplier and reset

Current xen-linux (2.6.18) not include support for Cx MWAIT entry method. Back port from latest Linux kernel (already there since 2.6.23). Without this patch, _CST method couldn''t get C states with FFH address space type. Signed-off-by: Wei Gang <gang.wei@intel.com> Jimmy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

There''re basically two methods to enter a given C-state: legacy (hlt + I/O read), and native(using mwait). MWAIT is always preferred when both underlying CPU and OS support, which is a more efficient way to conduct C-state transition. Xen PM relies on Dom0 to parse ACPI Cx/Px information, which involves one step to notify BIOS about a set of capabilities supported by OSPM. One capability

Hi, i''m not sure if i understood the new acpi xen cpufreq driver - here''s the output when loading xen_acpi_processor module in linux 3.4: dom0 dmesg: [ 32.728151] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU8 [ 32.728156] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU9 [ 32.728160] xen-acpi-processor: (CX): Hypervisor error (-22) for

On Thu, 2014-05-15 at 11:01 +0100, Ian Campbell wrote: > Please can you also post Xen's own dmesg (from "xl dmesg"). Please boot with loglvl=all on the hypervisor command line for this too. Ian.

...0 [ 5.238983] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2 [ 5.239021] ACPI: Sleep Button [SLPB] [ 5.239049] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [ 5.239074] ACPI: Power Button [PWRF] [ 5.239978] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-359) [ 5.239983] ACPI Error: Method parse/execution failed [\_PR_.CPU1._CST] (Node ffff8802218fedf8), AE_NOT_FOUND (20131115/psparse-536) [ 5.240436] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-...

...0 [ 5.238983] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2 [ 5.239021] ACPI: Sleep Button [SLPB] [ 5.239049] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [ 5.239074] ACPI: Power Button [PWRF] [ 5.239978] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-359) [ 5.239983] ACPI Error: Method parse/execution failed [\_PR_.CPU1._CST] (Node ffff8802218fedf8), AE_NOT_FOUND (20131115/psparse-536) [ 5.240436] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-...

Hello, The following patches are a solution to a problem we have encountered when using the Xen hypervisor: - Need Pxx/Cxx states to save on power consumption when using Xen (we do want those datacenters to consume less power!), - Also need to figure out the Turbo mode so that the scheduler can properly boost a core for CPU bound guests. In essence the Xen hypervisor requires that