How to use deeper C state

All of lore.kernel.org
 help / color / mirror / Atom feed

* How to use deeper C state
@ 2009-01-21  9:02 Akio Takebe
  2009-01-21  9:10 ` Keir Fraser
  2009-01-21  9:24 ` Wei, Gang
  0 siblings, 2 replies; 7+ messages in thread
From: Akio Takebe @ 2009-01-21  9:02 UTC (permalink / raw)
  To: xen-devel; +Cc: Tian, Kevin, Yu, Ke

Hi,

When I tried cpuidle option,
max_cstate indicates C7 with debug-key in my machine.
But the result of "xenpm start" doesn't say
that xen enter C2 or more state.
Do I need anything else(boot option and so on)?


(XEN) ==cpu0==
(XEN) active state:             C1
(XEN) max_cstate:               C7
(XEN) states:
(XEN)    *C1:   type[C1] latency[000] usage[00409594] duration
[1893990621775]
(XEN)     C0:   usage[00409594] duration[22279357433]
(XEN) ==cpu1==
(XEN) active state:             C1
(XEN) max_cstate:               C7
(XEN) states:
(XEN)    *C1:   type[C1] latency[000] usage[00396768] duration
[1891756608514]
(XEN)     C0:   usage[00396768] duration[24513377367]

# xenpm start
Elapsed time (ms): 466915
CPU0:
        residency       percentage
  C0    220 ms  0.05%
  C1    466695 ms       99.95%
  P0    60 ms   100.00%
  P1    0 ms    0.00%

CPU1:
        residency       percentage
  C0    606 ms  0.13%
  C1    466309 ms       99.87%
  P0    450 ms  100.00%
  P1    0 ms    0.00%


Best Regards,

Akio Takebe

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: How to use deeper C state
  2009-01-21  9:02 How to use deeper C state Akio Takebe
@ 2009-01-21  9:10 ` Keir Fraser
  2009-01-21  9:27   ` Wei, Gang
  2009-01-21  9:24 ` Wei, Gang
  1 sibling, 1 reply; 7+ messages in thread
From: Keir Fraser @ 2009-01-21  9:10 UTC (permalink / raw)
  To: Akio Takebe, xen-devel; +Cc: Tian, Kevin, Yu, Ke

On 21/01/2009 09:02, "Akio Takebe" <takebe_akio@jp.fujitsu.com> wrote:

> When I tried cpuidle option,
> max_cstate indicates C7 with debug-key in my machine.
> But the result of "xenpm start" doesn't say
> that xen enter C2 or more state.
> Do I need anything else(boot option and so on)?
> 

Try adding hpetbroadcast to your Xen command line.

 -- Keir

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: How to use deeper C state
  2009-01-21  9:10 ` Keir Fraser
@ 2009-01-21  9:27   ` Wei, Gang
  0 siblings, 0 replies; 7+ messages in thread
From: Wei, Gang @ 2009-01-21  9:27 UTC (permalink / raw)
  To: Keir Fraser, Akio Takebe, xen-devel; +Cc: Tian, Kevin, Yu, Ke

On Wednesday, January 21, 2009 5:10 PM, Keir Fraser wrote:
> On 21/01/2009 09:02, "Akio Takebe" <takebe_akio@jp.fujitsu.com> wrote:
> 
>> When I tried cpuidle option,
>> max_cstate indicates C7 with debug-key in my machine.
>> But the result of "xenpm start" doesn't say
>> that xen enter C2 or more state.
>> Do I need anything else(boot option and so on)?
>> 
> 
> Try adding hpetbroadcast to your Xen command line.

The hpetbroadcast doesn't help on this. Please give the entired xm dmesg as I mentioned in another reply.

Jimmy

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: How to use deeper C state
  2009-01-21  9:02 How to use deeper C state Akio Takebe
  2009-01-21  9:10 ` Keir Fraser
@ 2009-01-21  9:24 ` Wei, Gang
  2009-01-21  9:35   ` Akio Takebe
  1 sibling, 1 reply; 7+ messages in thread
From: Wei, Gang @ 2009-01-21  9:24 UTC (permalink / raw)
  To: Akio Takebe, xen-devel; +Cc: Tian, Kevin, Yu, Ke

The max_cstate just means if there are c-state deep to C7, those deep C states can be entered. But from below debug out, I found the deepest C state supported is C1 in you machine because all supported C states will be printed out.

You machine may not support deep C states, or dom0 failed to detected it from BIOS. Can you provide the whole 'xm dmesg' result right after booting up?

Jimmy

On Wednesday, January 21, 2009 5:03 PM, Akio Takebe wrote:
> Hi,
> 
> When I tried cpuidle option,
> max_cstate indicates C7 with debug-key in my machine.
> But the result of "xenpm start" doesn't say
> that xen enter C2 or more state.
> Do I need anything else(boot option and so on)?
> 
> 
> (XEN) ==cpu0==
> (XEN) active state:             C1
> (XEN) max_cstate:               C7
> (XEN) states:
> (XEN)    *C1:   type[C1] latency[000] usage[00409594] duration
> [1893990621775]
> (XEN)     C0:   usage[00409594] duration[22279357433]
> (XEN) ==cpu1==
> (XEN) active state:             C1
> (XEN) max_cstate:               C7
> (XEN) states:
> (XEN)    *C1:   type[C1] latency[000] usage[00396768] duration
> [1891756608514]
> (XEN)     C0:   usage[00396768] duration[24513377367]
> 
> # xenpm start
> Elapsed time (ms): 466915
> CPU0:
>         residency       percentage
>   C0    220 ms  0.05%
>   C1    466695 ms       99.95%
>   P0    60 ms   100.00%
>   P1    0 ms    0.00%
> 
> CPU1:
>         residency       percentage
>   C0    606 ms  0.13%
>   C1    466309 ms       99.87%
>   P0    450 ms  100.00%
>   P1    0 ms    0.00%
> 
> 
> Best Regards,
> 
> Akio Takebe
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: How to use deeper C state
  2009-01-21  9:24 ` Wei, Gang
@ 2009-01-21  9:35   ` Akio Takebe
  2009-01-21 10:08     ` Wei, Gang
  0 siblings, 1 reply; 7+ messages in thread
From: Akio Takebe @ 2009-01-21  9:35 UTC (permalink / raw)
  To: Wei, Gang, xen-devel; +Cc: Tian, Kevin, Akio Takebe, Yu, Ke

Hi,

>The max_cstate just means if there are c-state deep to C7, those deep C 
>states can be entered. But from below debug out, I found the deepest C state 
>supported is C1 in you machine because all supported C states will be printed 
>out.
>
>You machine may not support deep C states, or dom0 failed to detected it from 
>BIOS. Can you provide the whole 'xm dmesg' result right after booting up?
>
Thank you for your reply.
The xm dmesg is below.

Best Regards,

Akio Takebe

# xm dmesg
 __  __            _____ _  _                      _        _     _      
 \ \/ /___ _ __   |___ /| || |     _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \    |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) |__   _|__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_) |_|     \__,_|_| |_|___/\__\__,_|_.__/|_|\___|

(XEN) Xen version 3.4-unstable (root@(none)) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) Wed Jan 21 17:15:00 JST 2009
(XEN) Latest ChangeSet: Tue Jan 20 16:41:29 2009 +0000 19063:a0dddcbd9e32
(XEN) Command line: loglvl=all guest_loglvl=all com1=115200,8n1 console=vga,com1 cpuidle=1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007d490000 (usable)
(XEN)  000000007d490000 - 000000007d4e3000 (ACPI NVS)
(XEN)  000000007d4e3000 - 000000007d4f0000 (ACPI data)
(XEN)  000000007d4f0000 - 000000007d500000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2004MB (2052280kB)
(XEN) ACPI: RSDP 000F89A0, 0024 (r2 FUJ   )
(XEN) ACPI: XSDT 7D4E3080, 006C (r1 FUJ    PC       30303231 AWRD        0)
(XEN) ACPI: FACP 7D4E8000, 00F4 (r3 FUJ    PC       30303231 AWRD        0)
(XEN) ACPI: DSDT 7D4E3200, 4DC1 (r1 FUJ    AWRDACPI      201 MSFT  3000000)
(XEN) ACPI: FACS 7D490000, 0040
(XEN) ACPI: SLIC 7D4E8200, 0176 (r1 FUJ    PC       30303231 AWRD  1010101)
(XEN) ACPI: ASF! 7D4E8400, 008A (r16 FUJ    PC       30303231 AWRD        0)
(XEN) ACPI: HPET 7D4E8380, 0038 (r1 FUJ    PC       30303231 AWRD       98)
(XEN) ACPI: MCFG 7D4E83C0, 003C (r1 FUJ    PC       30303231 AWRD        0)
(XEN) ACPI: APIC 7D4E8100, 0084 (r1 FUJ    PC       30303231 AWRD        0)
(XEN) ACPI: SSDT 7D4E8B20, 07EF (r1  PmRef    CpuPm     3000 INTL 20061109)
(XEN) ACPI: BOOT 7D4E9340, 0028 (r1 FUJ    PC       30303231 AWRD        0)
(XEN) ACPI: DMAR 7D4E9380, 0110 (r1 IntelR AWRDACPI 322E3030 DRWA        2)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000007d490000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000f42e0
(XEN) DMI 2.5 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI:                  wakeup_vec[7d49000c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2992.902 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 4096K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz stepping 0b
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 4096K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) MCE: Intel newly family MC Init
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz stepping 0b
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation disabled
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Init_mcheck_timer
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff805c190c
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000079000000->000000007a000000 (470209 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff805c190c
(XEN)  Init. ramdisk: ffffffff805c2000->ffffffff80b73000
(XEN)  Phys-Mach map: ffffffff80b73000->ffffffff80f11608
(XEN)  Start info:    ffffffff80f12000->ffffffff80f124b4
(XEN)  Page tables:   ffffffff80f13000->ffffffff80f1e000
(XEN)  Boot stack:    ffffffff80f1e000->ffffffff80f1f000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81000000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 108kB init memory.
(XEN) io_apic.c:2211: 
(XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4
(XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) PCI add device 00:00.0
(XEN) PCI add device 00:01.0
(XEN) PCI add device 00:02.0
(XEN) PCI add device 00:03.0
(XEN) PCI add device 00:03.2
(XEN) PCI add device 00:03.3
(XEN) PCI add device 00:19.0
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1b.0
(XEN) PCI add device 00:1c.0
(XEN) PCI add device 00:1c.4
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1e.0
(XEN) PCI add device 00:1f.0
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 01:00.0
(XEN) PCI add device 01:00.1
(XEN) PCI add device 03:00.0
(XEN) PCI add device 00:03.2
(XEN) PCI add device 03:00.0
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 00:19.0
(XEN) PCI add device 01:00.0
(XEN) PCI add device 00:1b.0
(XEN) PCI add device 01:00.1
(XEN) Set CPU acpi_id(0) cpuid(0) Px State info:
(XEN)   _PPC: 0
(XEN) cpu0 cx acpi info:
(XEN)   count = 1
(XEN)   flags: bm_cntl[0], bm_chk[0], has_cst[0],
(XEN)          pwr_setup_done[1], bm_rld_set[0]
(XEN)   states[0]:
(XEN)           reg.space_id = 0x0
(XEN)           reg.bit_width = 0x0
(XEN)           reg.bit_offset = 0x0
(XEN)           reg.access_size = 0x0
(XEN)           reg.address = 0x0
(XEN)           type    = 1
(XEN)           latency = 0
(XEN)           power   = 0
(XEN)           dp(@0x0000000000000000)
(XEN) ==cpu0==
(XEN) active state:             C-1
(XEN) max_cstate:               C7
(XEN) states:
(XEN)     C1:   type[C1] latency[000] usage[00000000] duration[0]
(XEN)     C0:   usage[00000000] duration[41067564046]
(XEN) Set CPU acpi_id(0) cpuid(0) Px State info:
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0, reserved=0, address=0
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0, reserved=0, address=0
(XEN)   _PSS: state_count=2
(XEN)   State0: 2997MHz 88000mW 10us 10us 0x92a 0x92a
(XEN)   State1: 1998MHz 54000mW 10us 10us 0x61b 0x61b
(XEN)   _PSD: num_entries=5 rev=0 domain=0 coord_type=252 num_processors=1
(XEN)   _PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 0 initialization completed
(XEN) Set CPU acpi_id(1) cpuid(1) Px State info:
(XEN)   _PPC: 0
(XEN) cpu1 cx acpi info:
(XEN)   count = 1
(XEN)   flags: bm_cntl[0], bm_chk[0], has_cst[0],
(XEN)          pwr_setup_done[1], bm_rld_set[0]
(XEN)   states[0]:
(XEN)           reg.space_id = 0x0
(XEN)           reg.bit_width = 0x0
(XEN)           reg.bit_offset = 0x0
(XEN)           reg.access_size = 0x0
(XEN)           reg.address = 0x0
(XEN)           type    = 1
(XEN)           latency = 0
(XEN)           power   = 0
(XEN)           dp(@0x0000000000000000)
(XEN) ==cpu1==
(XEN) active state:             C-1
(XEN) max_cstate:               C7
(XEN) states:
(XEN)     C1:   type[C1] latency[000] usage[00000000] duration[0]
(XEN)     C0:   usage[00000000] duration[41068216773]
(XEN) Set CPU acpi_id(1) cpuid(1) Px State info:
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0, reserved=0, address=0
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0, reserved=0, address=0
(XEN)   _PSS: state_count=2
(XEN)   State0: 2997MHz 88000mW 10us 10us 0x92a 0x92a
(XEN)   State1: 1998MHz 54000mW 10us 10us 0x61b 0x61b
(XEN)   _PSD: num_entries=5 rev=0 domain=1 coord_type=252 num_processors=1
(XEN)   _PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 1 initialization completed
(XEN) cpu2 cx acpi info:
(XEN)   count = 1
(XEN)   flags: bm_cntl[0], bm_chk[0], has_cst[0],
(XEN)          pwr_setup_done[1], bm_rld_set[0]
(XEN)   states[0]:
(XEN)           reg.space_id = 0x0
(XEN)           reg.bit_width = 0x0
(XEN)           reg.bit_offset = 0x0
(XEN)           reg.access_size = 0x0
(XEN)           reg.address = 0x0
(XEN)           type    = 1
(XEN)           latency = 0
(XEN)           power   = 0
(XEN)           dp(@0x0000000000000000)
(XEN) no cpu_id for acpi_id 2
(XEN) cpu3 cx acpi info:
(XEN)   count = 1
(XEN)   flags: bm_cntl[0], bm_chk[0], has_cst[0],
(XEN)          pwr_setup_done[1], bm_rld_set[0]
(XEN)   states[0]:
(XEN)           reg.space_id = 0x0
(XEN)           reg.bit_width = 0x0
(XEN)           reg.bit_offset = 0x0
(XEN)           reg.access_size = 0x0
(XEN)           reg.address = 0x0
(XEN)           type    = 1
(XEN)           latency = 0
(XEN)           power   = 0
(XEN)           dp(@0x0000000000000000)
(XEN) no cpu_id for acpi_id 3

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: How to use deeper C state
  2009-01-21  9:35   ` Akio Takebe
@ 2009-01-21 10:08     ` Wei, Gang
  2009-01-21 10:14       ` Akio Takebe
  0 siblings, 1 reply; 7+ messages in thread
From: Wei, Gang @ 2009-01-21 10:08 UTC (permalink / raw)
  To: Akio Takebe, xen-devel; +Cc: Tian, Kevin, Yu, Ke

On Wednesday, January 21, 2009 5:35 PM, Akio Takebe wrote:
> Hi,
> 
>> The max_cstate just means if there are c-state deep to C7, those deep C
>> states can be entered. But from below debug out, I found the deepest C state
>> supported is C1 in you machine because all supported C states will be
>> printed out. 
>> 
>> You machine may not support deep C states, or dom0 failed to detected it from
>> BIOS. Can you provide the whole 'xm dmesg' result right after booting up?
>> 
> Thank you for your reply.
> The xm dmesg is below.
>...
> 
> (XEN) cpu1 cx acpi info:
> (XEN)   count = 1
> (XEN)   flags: bm_cntl[0], bm_chk[0], has_cst[0],
> (XEN)          pwr_setup_done[1], bm_rld_set[0]
> (XEN)   states[0]:
> (XEN)           reg.space_id = 0x0
> (XEN)           reg.bit_width = 0x0
> (XEN)           reg.bit_offset = 0x0
> (XEN)           reg.access_size = 0x0
> (XEN)           reg.address = 0x0
> (XEN)           type    = 1
> (XEN)           latency = 0
> (XEN)           power   = 0
> (XEN)           dp(@0x0000000000000000)

Yes, dom0 only detected and passed one C state to HV. Can you give the machine model? Meanwhile please have some checks on CMOS options for whether there are some C-state or ACPI related options which are not enabled. 

Jimmy

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: How to use deeper C state
  2009-01-21 10:08     ` Wei, Gang
@ 2009-01-21 10:14       ` Akio Takebe
  0 siblings, 0 replies; 7+ messages in thread
From: Akio Takebe @ 2009-01-21 10:14 UTC (permalink / raw)
  To: Wei, Gang, xen-devel; +Cc: Tian, Kevin, Akio Takebe, Yu, Ke

Hi,

>On Wednesday, January 21, 2009 5:35 PM, Akio Takebe wrote:
>> Hi,
>> 
>>> The max_cstate just means if there are c-state deep to C7, those deep C
>>> states can be entered. But from below debug out, I found the deepest C 
>>> state
>>> supported is C1 in you machine because all supported C states will be
>>> printed out. 
>>> 
>>> You machine may not support deep C states, or dom0 failed to detected it 
>>> from
>>> BIOS. Can you provide the whole 'xm dmesg' result right after booting up?
>>> 
>> Thank you for your reply.
>> The xm dmesg is below.
>>...
>> 
>> (XEN) cpu1 cx acpi info:
>> (XEN)   count = 1
>> (XEN)   flags: bm_cntl[0], bm_chk[0], has_cst[0],
>> (XEN)          pwr_setup_done[1], bm_rld_set[0]
>> (XEN)   states[0]:
>> (XEN)           reg.space_id = 0x0
>> (XEN)           reg.bit_width = 0x0
>> (XEN)           reg.bit_offset = 0x0
>> (XEN)           reg.access_size = 0x0
>> (XEN)           reg.address = 0x0
>> (XEN)           type    = 1
>> (XEN)           latency = 0
>> (XEN)           power   = 0
>> (XEN)           dp(@0x0000000000000000)
>
>Yes, dom0 only detected and passed one C state to HV. Can you give the 
>machine model? Meanwhile please have some checks on CMOS options for whether 
>there are some C-state or ACPI related options which are not enabled. 
>
Thank you very much. I'll check some BIOS menu.

Best Regards,

Akio Takebe

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2009-01-21 10:14 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-21  9:02 How to use deeper C state Akio Takebe
2009-01-21  9:10 ` Keir Fraser
2009-01-21  9:27   ` Wei, Gang
2009-01-21  9:24 ` Wei, Gang
2009-01-21  9:35   ` Akio Takebe
2009-01-21 10:08     ` Wei, Gang
2009-01-21 10:14       ` Akio Takebe

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.