search for: _ppc

...ocessor: cache acpi_power_register in cx structure ACPI: processor: Don''t setup cpu idle driver and handler when we do not want them. ACPI: add processor driver for Xen virtual CPUs. ACPI: xen processor: add PM notification interfaces. ACPI: xen processor: set ignore_ppc to handle PPC event for Xen vcpu. Tang Liang (2): ACPI: processor: add __acpi_processor_[un]register_driver helpers. ACPI: processor: override the interface of register acpi processor handler for Xen vcpu drivers/acpi/Makefile | 1 + drivers/acpi/processor_driver.c |...

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 everyone, When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If I turn CONFIG_INTEL_IDLE off then the boot goes well and, after dom0 has booted, xenpm works and gives some sane output, see below. I have tested this with kernels 3.2 to 3.4.6. Is it impossible to use INTEL_IDLE with Xen? If this is a known issue then maybe

Hi everyone, When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If I turn CONFIG_INTEL_IDLE off then the boot goes well and, after dom0 has booted, xenpm works and gives some sane output, see below. I have tested this with kernels 3.2 to 3.4.6. Is it impossible to use INTEL_IDLE with Xen? If this is a known issue then maybe

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.

...ce) [ 0.107604] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.107605] ACPI: Added _OSI(Processor Aggregator Device) [ 0.109626] ACPI: Executed 1 blocks of module-level executable AML code [ 0.133067] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 0.133400] ACPI Error: [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-359) [ 0.133403] ACPI Error: Method parse/execution failed [\_PR_.CPU0._PDC] (Node ffff8802360f7da8), AE_NOT_FOUND (20131115/psparse-536) [ 0.133552] ACPI: SSDT 00000000bedbad98 000119 (v01 PmRef ApCst 00003000 INTL 20100331) [ 0...

...ce) [ 2.012045] ACPI: Added _OSI(3.0 _SCP Extensions) [ 2.012046] ACPI: Added _OSI(Processor Aggregator Device) [ 2.014090] ACPI: Executed 1 blocks of module-level executable AML code [ 2.036501] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 2.036904] ACPI Error: [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-359) [ 2.036908] ACPI Error: Method parse/execution failed [\_PR_.CPU0._PDC] (Node ffff8802218e5da8), AE_NOT_FOUND (20131115/psparse-536) [ 2.037051] ACPI: SSDT 00000000bedbad98 000119 (v01 PmRef ApCst 00003000 INTL 20100331) [ 2...

...B_RTYP 3510: a0 16 90 44 54 53 45 94 54 43 4e 54 01 54 52 41 ...DTSE.TCNT.TRA 3520: 50 54 52 54 44 0a 14 a0 4b 0b 93 4f 53 59 53 0b PTRTD...K..OSYS. 3530: d2 07 a0 40 0b 7b 43 46 47 44 01 00 a0 4b 05 94 ... at .{CFGD...K.. 3540: 5c 2f 03 5f 50 52 5f 43 50 55 30 5f 50 50 43 00 \/._PR_CPU0_PPC. 3550: 74 5c 2f 03 5f 50 52 5f 43 50 55 30 5f 50 50 43 t\/._PR_CPU0_PPC 3560: 01 5c 2f 03 5f 50 52 5f 43 50 55 30 5f 50 50 43 .\/._PR_CPU0_PPC 3570: 50 4e 4f 54 72 5c 2f 03 5f 50 52 5f 43 50 55 30 PNOTr\/._PR_CPU0 3580: 5f 50 50 43 01 5c 2f 03 5f 50 52 5f 43 50 55 30 _PPC.\/._PR_CPU0...