Is there a way for me to tell if the Centos kernel has those
modifications? A kernel config option or something?
The xenpm wiki page shows an extract for xm dmesg, but there is nothing
like that in my xm dmesg output. Is it possible that there is something
missing from the gitco Xen build?
Mike
On Thu, 2009-06-04 at 18:53 +0800, Wei, Gang wrote:
> The dom0 kernel need to be modified to pass acpi info about C/P states to
> Xen. Xen depends on dom0 to get those information.
>
> Jimmy
>
> Mike Brady wrote:
> > I have just tried that. It has made no difference.
> >
> > May be the Centos kernel does not have something that is required.
> > What needs to be enabled in the Dom0 kernel for PM to work?
> >
> > On Thu, 2009-06-04 at 18:05 +0800, Wei, Gang wrote:
> >> Can you try with removing "dom0_max_vcpus=1" from the grub
> > line? I suspect this is a dom0 kernel issue. The upstream
> > 2.6.18 xen-linux kernel works well as dom0 kernel with PM. I
> > am not sure about Centos 5.3 kernel.
> >>
> >> Jimmy
> >>
> >> Mike Brady wrote:
> >>> The BIOS has the following options, both of which are enabled:
> >>> - Intel Speed Step
> >>> - Deep C-State Support
> >>>
> >>> As reported by /proc/cpuinfo the cpu speed does vary using a native
> >>> Linux kernel.
> >>>
> >>> Sorry but I am not in a position to do my own build at the moment.
> >>> I may be able to try it next week.
> >>>
> >>> Thanks
> >>>
> >>> Mike
> >>>
> >>> On Thu, 2009-06-04 at 16:41 +0800, Wei, Gang wrote:
> >>>> Hi, Mike,
> >>>>
> >>>> Are there any BIOS options in your box related with C-states
> >>> or P-states? These may be disabled.
> >>>>
> >>>> Or can you try the native Linux first to make sure you can see the
> >>>> PM effect?
> >>>>
> >>>> Further, if you can rebuild Xen yourself, please turn on the
> >>> C/P state debug flag ( e.g. uncomment/*#define DEBUG_PM_CX*/
> >>> in cpu_idle.c) , and repost the serial log for more detail info.
> >>>>
> >>>> Jimmy
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> >>>>> Sent: 2009年6月4日 15:47
> >>>>> To: mike.brady@xxxxxxxxxxxxxx; xen-devel
> >>>>> Cc: Wei, Gang
> >>>>> Subject: Re: [Xen-devel] [Fwd: Problems with power management]
> >>>>>
> >>>>> Your best bet tool here is 'hg -v history tools/misc/xenpm.c |
> >>>>> less' and pick one of the developers of the component. In this
> >>>>> case Wei Gang would be plausible (cc'ed).
> >>>>>
> >>>>> -- Keir
> >>>>>
> >>>>> On 04/06/2009 06:40, "Mike Brady"
> > <mike.brady@xxxxxxxxxxxxxx> wrote:
> >>>>>
> >>>>>> I posted this on the user list but it has been suggested to me
> >>>>>> that it may pay to ask on the devel list as well as I didn't get
> >>>>>> any responses.
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>> Mike
> >>>>>>
> >>>>>> -------- Forwarded Message --------
> >>>>>>> From: Mike Brady <mike.brady@xxxxxxxxxxxxxx>
> >>>>>>> Reply-To: mike.brady@xxxxxxxxxxxxxx
> >>>>>>> To: xen-users@xxxxxxxxxxxxxxxxxxx
> > <xen-users@xxxxxxxxxxxxxxxxxxx>
> >>>>>>> Subject: Problems with power management
> >>>>>>> Date: Sat, 30 May 2009 16:28:11 +1200
> >>>>>>>
> >>>>>>> I do not seem to be able to get any where with the power
> >>>>>>> management functions. I have had a look at the xenpm Wiki page,
> >>>>>>> but it hasn't helped. Its probably something completely
> >>>>>>> obvious, but I can't see it.
> >>>>>>>
> >>>>>>> I running Xen 3.4.0 on Centos 5.3 x86_64 using the gitco RPMs on
> >>>>>>> an Intel S5000PSL motherboard with 2 x Xeon 5410s. Dom0 is
> >>>>>>> running the latest Centos 5.3 kernel.
> >>>>>>>
> >>>>>>> My xm dmesg output is below followed by the output that I get
> >>>>>>> from the xenpm get* commands, which isn't much.
> >>>>>>>
> >>>>>>> ============================================
> >>>>>>> [root@b52 ~]# xm dmesg
> >>>>>>> __ __ _____ _ _ ___
> >>>>>>> \ \/ /___ _ __ |___ /| || | / _ \
> >>>>>>> \ // _ \ '_ \ |_ \| || |_| | | |
> >>>>>>> / \ __/ | | | ___) |__ _| |_| |
> >>>>>>> /_/\_\___|_| |_| |____(_) |_|(_)___/
> >>>>>>>
> >>>>>>> (XEN) Xen version 3.4.0 (root@xxxxxxxxx) (gcc version 4.1.2
> >>>>>>> 20080704 (Red Hat 4.1.2-44)) Wed May 27 21:53:09 CEST 2009
> >>>>>>> (XEN) Latest ChangeSet: unavailable
> >>>>>>> (XEN) Command line: cpufreq=xen cpuidle dom0_max_vcpus=1
> >>>>>>> dom0_vcpus_pin=true dom0_mem=1024M
> >>> apic_verbosity=verbose loglvl=all
> >>>>>>> (XEN) Video information:
> >>>>>>> (XEN) VGA is text mode 80x25, font 8x16
> >>>>>>> (XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds
> >>>>>>> (XEN) EDID info not retrieved because no DDC retrieval method
> >>>>>>> detected (XEN) Disc information: (XEN) Found 2 MBR signatures
> >>>>>>> (XEN) Found 2 EDD information structures
> >>>>>>> (XEN) Xen-e820 RAM map:
> >>>>>>> (XEN) 0000000000000000 - 000000000009f400 (usable)
> >>>>>>> (XEN) 000000000009f400 - 0000000000100000 (reserved)
> >>>>>>> (XEN) 0000000000100000 - 000000009e2e1000 (usable)
> >>>>>>> (XEN) 000000009e2e1000 - 000000009e3a3000 (ACPI NVS)
> >>>>>>> (XEN) 000000009e3a3000 - 000000009fa32000 (usable)
> >>>>>>> (XEN) 000000009fa32000 - 000000009fa9a000 (reserved)
> >>>>>>> (XEN) 000000009fa9a000 - 000000009faac000 (usable)
> >>>>>>> (XEN) 000000009faac000 - 000000009fb1a000 (ACPI NVS)
> >>>>>>> (XEN) 000000009fb1a000 - 000000009fb26000 (usable)
> >>>>>>> (XEN) 000000009fb26000 - 000000009fb3a000 (ACPI data)
> >>>>>>> (XEN) 000000009fb3a000 - 000000009fc00000 (usable)
> >>>>>>> (XEN) 000000009fc00000 - 00000000b0000000 (reserved)
> >>>>>>> (XEN) 00000000ffc00000 - 00000000ffc0c000 (reserved)
> >>>>>>> (XEN) 0000000100000000 - 0000000260000000 (usable)
> >>>>>>> (XEN) System RAM: 8185MB (8382412kB)
> >>>>>>> (XEN) ACPI: RSDP 000F03C0, 0024 (r2 INTEL )
> >>>>>>> (XEN) ACPI: XSDT 9FB39120, 0084 (r1 INTEL S5000PSL
> > 0 INTL
> >>>>>>> 1000013) (XEN) ACPI: FACP 9FB37000, 00F4 (r3 INTEL S5000PSL
> >>>>>>> 0 INTL 1000013) (XEN) ACPI: DSDT 9FB30000, 57F6 (r2 INTEL
> >>>>>>> S5000PSL 1 INTL 1000013) (XEN) ACPI: FACS 9FAAC000, 0040
> >>>>>>> (XEN) ACPI: APIC 9FB36000, 00C8 (r1 INTEL S5000PSL
> > 0 INTL
> >>>>>>> 1000013) (XEN) ACPI: SPCR 9FB2F000, 0050 (r1 INTEL S5000PSL
> >>>>>>> 0 INTL 1000013) (XEN) ACPI: HPET 9FB2E000, 0038 (r1 INTEL
> >>>>>>> S5000PSL 1 INTL 1000013) (XEN) ACPI: MCFG 9FB2D000, 003C
> >>>>>>> (r1 INTEL S5000PSL 1 INTL 1000013) (XEN) ACPI: SSDT
> >>>>>>> 9FB2C000, 0A14 (r2 INTEL EIST 4000 INTL 1000013) (XEN)
> >>>>>>> ACPI: SSDT 9FB2B000, 0193 (r2 INTEL IPMI 4000 INTL
> >>>>>>> 1000013) (XEN) ACPI: SSDT 9FB2A000, 00CE (r2 INTEL CST
> >>>>>>> 4000 INTL 1000013) (XEN) ACPI: HEST 9FB29000, 00A8 (r1 INTEL
> >>>>>>> S5000PSL 1 INTL 1) (XEN) ACPI: BERT 9FB28000, 0030 (r1
> >>>>>>> INTEL S5000PSL 1 INTL 1) (XEN) ACPI: ERST 9FB27000, 0230
> >>>>>>> (r1 INTEL S5000PSL 1 INTL 1) (XEN) ACPI: EINJ 9FB26000,
> >>>>>>> 0130 (r1 INTEL S5000PSL 1 INTL 1) (XEN) NUMA turned off
> >>>>>>> (XEN) Faking a node at 0000000000000000-0000000260000000 (XEN)
> >>>>>>> Domain heap initialised (XEN) found SMP MP-table at 000fd190
> >>>>>>> (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[9faac00c], vec_size[20]
> >>>>>>> (XEN) ACPI: Local APIC address 0xfee00000
> >>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> >>>>>>> (XEN) Processor #0 7:7 APIC version 20
> >>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled)
> >>>>>>> (XEN) Processor #2 7:7 APIC version 20
> >>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled)
> >>>>>>> (XEN) Processor #4 7:7 APIC version 20
> >>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled)
> >>>>>>> (XEN) Processor #6 7:7 APIC version 20
> >>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled)
> >>>>>>> (XEN) Processor #1 7:7 APIC version 20
> >>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled)
> >>>>>>> (XEN) Processor #3 7:7 APIC version 20
> >>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
> >>>>>>> (XEN) Processor #5 7:7 APIC version 20
> >>>>>>> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
> >>>>>>> (XEN) Processor #7 7:7 APIC version 20
> >>>>>>> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1])
> >>>>>>> (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1])
> >>>>>>> (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1])
> >>>>>>> (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1])
> >>>>>>> (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1])
> >>>>>>> (XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1])
> >>>>>>> (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1])
> >>>>>>> (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1])
> >>>>>>> (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
> >>>>>>> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI
> >>>>>>> 0-23 (XEN) ACPI: IOAPIC (id[0x09] address[0xfec80000]
> >>>>>>> gsi_base[24]) (XEN) IOAPIC[1]: apic_id 9, version 32, address
> >>>>>>> 0xfec80000, GSI 24-47 (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 2 I/O APICs
> >>>>>>> (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
> >>>>>>> (XEN) Using ACPI (MADT) for SMP configuration information
> >>>>>>> (XEN) mapped APIC to ffff828bffffe000 (fee00000)
> >>>>>>> (XEN) mapped IOAPIC to ffff828bffffd000 (fec00000)
> >>>>>>> (XEN) mapped IOAPIC to ffff828bffffc000 (fec80000)
> >>>>>>> (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN)
> >>>>>>> Initializing CPU#0 (XEN) Detected 2327.591 MHz processor.
> >>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>>>>>> (XEN) CPU: L2 cache: 6144K
> >>>>>>> (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) 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) Xeon(R) CPU E5410 @ 2.33GHz
> >>>>>>> stepping 06 (XEN) enabled ExtINT on CPU#0 (XEN) Booting
> >>>>>>> processor 1/2 eip 8c000 (XEN) Initializing CPU#1
> >>>>>>> (XEN) masked ExtINT on CPU#1
> >>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>>>>>> (XEN) CPU: L2 cache: 6144K
> >>>>>>> (XEN) CPU: Physical Processor ID: 0
> >>>>>>> (XEN) CPU: Processor Core ID: 2
> >>>>>>> (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) Xeon(R) CPU E5410 @ 2.33GHz
> >>>>>>> stepping 06 (XEN) Booting processor 2/4 eip 8c000
> >>>>>>> (XEN) Initializing CPU#2
> >>>>>>> (XEN) masked ExtINT on CPU#2
> >>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>>>>>> (XEN) CPU: L2 cache: 6144K
> >>>>>>> (XEN) CPU: Physical Processor ID: 1
> >>>>>>> (XEN) CPU: Processor Core ID: 0
> >>>>>>> (XEN) Intel machine check reporting enabled on CPU#2.
> >>>>>>> (XEN) CPU2: Thermal monitoring enabled (TM2)
> >>>>>>> (XEN) CMCI: CPU2 has no CMCI support
> >>>>>>> (XEN) CPU2: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
> >>>>>>> stepping 06 (XEN) Booting processor 3/6 eip 8c000
> >>>>>>> (XEN) Initializing CPU#3
> >>>>>>> (XEN) masked ExtINT on CPU#3
> >>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>>>>>> (XEN) CPU: L2 cache: 6144K
> >>>>>>> (XEN) CPU: Physical Processor ID: 1
> >>>>>>> (XEN) CPU: Processor Core ID: 2
> >>>>>>> (XEN) Intel machine check reporting enabled on CPU#3.
> >>>>>>> (XEN) CPU3: Thermal monitoring enabled (TM2)
> >>>>>>> (XEN) CMCI: CPU3 has no CMCI support
> >>>>>>> (XEN) CPU3: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
> >>>>>>> stepping 06 (XEN) Booting processor 4/1 eip 8c000
> >>>>>>> (XEN) Initializing CPU#4
> >>>>>>> (XEN) masked ExtINT on CPU#4
> >>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>>>>>> (XEN) CPU: L2 cache: 6144K
> >>>>>>> (XEN) CPU: Physical Processor ID: 0
> >>>>>>> (XEN) CPU: Processor Core ID: 1
> >>>>>>> (XEN) Intel machine check reporting enabled on CPU#4.
> >>>>>>> (XEN) CPU4: Thermal monitoring enabled (TM2)
> >>>>>>> (XEN) CMCI: CPU4 has no CMCI support
> >>>>>>> (XEN) CPU4: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
> >>>>>>> stepping 06 (XEN) Booting processor 5/3 eip 8c000
> >>>>>>> (XEN) Initializing CPU#5
> >>>>>>> (XEN) masked ExtINT on CPU#5
> >>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>>>>>> (XEN) CPU: L2 cache: 6144K
> >>>>>>> (XEN) CPU: Physical Processor ID: 0
> >>>>>>> (XEN) CPU: Processor Core ID: 3
> >>>>>>> (XEN) Intel machine check reporting enabled on CPU#5.
> >>>>>>> (XEN) CPU5: Thermal monitoring enabled (TM2)
> >>>>>>> (XEN) CMCI: CPU5 has no CMCI support
> >>>>>>> (XEN) CPU5: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
> >>>>>>> stepping 06 (XEN) Booting processor 6/5 eip 8c000
> >>>>>>> (XEN) Initializing CPU#6
> >>>>>>> (XEN) masked ExtINT on CPU#6
> >>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>>>>>> (XEN) CPU: L2 cache: 6144K
> >>>>>>> (XEN) CPU: Physical Processor ID: 1
> >>>>>>> (XEN) CPU: Processor Core ID: 1
> >>>>>>> (XEN) Intel machine check reporting enabled on CPU#6.
> >>>>>>> (XEN) CPU6: Thermal monitoring enabled (TM2)
> >>>>>>> (XEN) CMCI: CPU6 has no CMCI support
> >>>>>>> (XEN) CPU6: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
> >>>>>>> stepping 06 (XEN) Booting processor 7/7 eip 8c000
> >>>>>>> (XEN) Initializing CPU#7
> >>>>>>> (XEN) masked ExtINT on CPU#7
> >>>>>>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>>>>>> (XEN) CPU: L2 cache: 6144K
> >>>>>>> (XEN) CPU: Physical Processor ID: 1
> >>>>>>> (XEN) CPU: Processor Core ID: 3
> >>>>>>> (XEN) Intel machine check reporting enabled on CPU#7.
> >>>>>>> (XEN) CPU7: Thermal monitoring enabled (TM2)
> >>>>>>> (XEN) CMCI: CPU7 has no CMCI support
> >>>>>>> (XEN) CPU7: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
> >>>>>>> stepping 06 (XEN) Total of 8 processors activated.
> >>>>>>> (XEN) ENABLING IO-APIC IRQs
> >>>>>>> (XEN) -> Using new ACK method
> >>>>>>> (XEN) init IO_APIC IRQs
> >>>>>>> (XEN) IO-APIC (apicid-pin) 8-0, 8-16, 8-17, 8-18, 8-19, 8-20,
> >>>>>>> 8-21, 8-22, 8-23, 9-0, 9-1, 9-2, 9-3, 9-4, 9-5, 9-6, 9-7, 9-8,
> >>>>>>> 9-9, 9-10, 9-11, 9-12, 9-13, 9-14, 9-15, 9-16, 9-17, 9-18, 9-19,
> >>>>>>> 9-20, 9-21, 9-22, 9-23 not connected. (XEN) ..TIMER: vector=0xF0
> >>>>>>> apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) number of MP IRQ sources:
> >>>>>>> 15. (XEN) number of IO-APIC #8 registers: 24.
> >>>>>>> (XEN) number of IO-APIC #9 registers: 24.
> >>>>>>> (XEN) testing the IO APIC.......................
> >>>>>>> (XEN) IO APIC #8......
> >>>>>>> (XEN) .... register #00: 08000000
> >>>>>>> (XEN) ....... : physical APIC id: 08
> >>>>>>> (XEN) ....... : Delivery Type: 0
> >>>>>>> (XEN) ....... : LTS : 0
> >>>>>>> (XEN) .... register #01: 00170020
> >>>>>>> (XEN) ....... : max redirection entries: 0017
> >>>>>>> (XEN) ....... : PRQ implemented: 0
> >>>>>>> (XEN) ....... : IO APIC version: 0020
> >>>>>>> (XEN) .... IRQ redirection table:
> >>>>>>> (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> >>>>>>> (XEN) 00 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 01 001 01 0 0 0 0 0 1 1 20
> >>>>>>> (XEN) 02 001 01 0 0 0 0 0 1 1 F0
> >>>>>>> (XEN) 03 001 01 0 0 0 0 0 1 1 28
> >>>>>>> (XEN) 04 001 01 0 0 0 0 0 1 1 30
> >>>>>>> (XEN) 05 001 01 0 0 0 0 0 1 1 38
> >>>>>>> (XEN) 06 001 01 0 0 0 0 0 1 1 40
> >>>>>>> (XEN) 07 001 01 0 0 0 0 0 1 1 48
> >>>>>>> (XEN) 08 001 01 0 0 0 0 0 1 1 50
> >>>>>>> (XEN) 09 001 01 1 1 0 0 0 1 1 58
> >>>>>>> (XEN) 0a 001 01 0 0 0 0 0 1 1 60
> >>>>>>> (XEN) 0b 001 01 0 0 0 0 0 1 1 68
> >>>>>>> (XEN) 0c 001 01 0 0 0 0 0 1 1 70
> >>>>>>> (XEN) 0d 001 01 0 0 0 0 0 1 1 78
> >>>>>>> (XEN) 0e 001 01 0 0 0 0 0 1 1 88
> >>>>>>> (XEN) 0f 001 01 0 0 0 0 0 1 1 90
> >>>>>>> (XEN) 10 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 11 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 12 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 13 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 14 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 15 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 16 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 17 000 00 1 0 0 0 0 0 0 00 (XEN) IO
> >>>>>>> APIC #9...... (XEN) .... register #00: 09000000
> >>>>>>> (XEN) ....... : physical APIC id: 09
> >>>>>>> (XEN) ....... : Delivery Type: 0
> >>>>>>> (XEN) ....... : LTS : 0
> >>>>>>> (XEN) .... register #01: 00178020
> >>>>>>> (XEN) ....... : max redirection entries: 0017
> >>>>>>> (XEN) ....... : PRQ implemented: 1
> >>>>>>> (XEN) ....... : IO APIC version: 0020
> >>>>>>> (XEN) .... register #02: 09000000
> >>>>>>> (XEN) ....... : arbitration: 09
> >>>>>>> (XEN) .... register #03: 00000001
> >>>>>>> (XEN) ....... : Boot DT : 1
> >>>>>>> (XEN) .... IRQ redirection table:
> >>>>>>> (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> >>>>>>> (XEN) 00 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 01 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 02 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 03 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 04 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 05 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 06 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 07 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 08 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 09 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 0a 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 0b 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 0c 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 0d 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 0e 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 0f 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 10 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 11 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 12 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 13 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 14 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 15 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 16 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) 17 000 00 1 0 0 0 0 0 0 00
> >>>>>>> (XEN) Using vector-based indexing
> >>>>>>> (XEN) IRQ to pin mappings:
> >>>>>>> (XEN) IRQ240 -> 0:2
> >>>>>>> (XEN) IRQ32 -> 0:1
> >>>>>>> (XEN) IRQ40 -> 0:3
> >>>>>>> (XEN) IRQ48 -> 0:4
> >>>>>>> (XEN) IRQ56 -> 0:5
> >>>>>>> (XEN) IRQ64 -> 0:6
> >>>>>>> (XEN) IRQ72 -> 0:7
> >>>>>>> (XEN) IRQ80 -> 0:8
> >>>>>>> (XEN) IRQ88 -> 0:9
> >>>>>>> (XEN) IRQ96 -> 0:10
> >>>>>>> (XEN) IRQ104 -> 0:11
> >>>>>>> (XEN) IRQ112 -> 0:12
> >>>>>>> (XEN) IRQ120 -> 0:13
> >>>>>>> (XEN) IRQ136 -> 0:14
> >>>>>>> (XEN) IRQ144 -> 0:15
> >>>>>>> (XEN) .................................... done.
> >>>>>>> (XEN) Using local APIC timer interrupts.
> >>>>>>> (XEN) calibrating APIC timer ...
> >>>>>>> (XEN) ..... CPU clock speed is 2327.5697 MHz.
> >>>>>>> (XEN) ..... host bus clock speed is 332.5098 MHz.
> >>>>>>> (XEN) ..... bus_scale = 0x00015489
> >>>>>>> (XEN) checking TSC synchronization across 8 CPUs: passed.
> >>>>>>> (XEN) Platform timer is 14.318MHz HPET
> >>>>>>> (XEN) Brought up 8 CPUs
> >>>>>>> (XEN) I/O virtualisation disabled
> >>>>>>> (XEN) HPET: 3 timers in total, 0 timers will be used for
> >>>>>>> broadcast (XEN) ACPI sleep modes: S3 (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 ->
> >>>>>>> 0xffffffff8074310c (XEN) PHYSICAL MEMORY ARRANGEMENT:
> >>>>>>> (XEN) Dom0 alloc.:
> > 0000000256000000->0000000258000000 (253952
> >>>>>>> pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT:
> >>>>>>> (XEN) Loaded kernel: ffffffff80200000->ffffffff8074310c
> >>>>>>> (XEN) Init. ramdisk: ffffffff80744000->ffffffff80f63a00
> >>>>>>> (XEN) Phys-Mach map: ffffffff80f64000->ffffffff81164000
> >>>>>>> (XEN) Start info: ffffffff81164000->ffffffff811644b4
> >>>>>>> (XEN) Page tables: ffffffff81165000->ffffffff81172000
> >>>>>>> (XEN) Boot stack: ffffffff81172000->ffffffff81173000
> >>>>>>> (XEN) TOTAL: ffffffff80000000->ffffffff81400000
> >>>>>>> (XEN) ENTRY ADDRESS: ffffffff80200000
> >>>>>>> (XEN) Dom0 has maximum 1 VCPUs
> >>>>>>> (XEN) Scrubbing Free
> >>>>>>> RAM:
> >>>>>>>
> >>> ...............................................................
> >>> .......do
> >>>>> ne.
> >>>>>>> (XEN) Xen trace buffers: disabled
> >>>>>>> (XEN) Std. Loglevel: All
> >>>>>>> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and
> >>>>>>> warnings) (XEN) Xen is relinquishing VGA console.
> >>>>>>> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to
> >>>>>>> switch input to Xen) (XEN) Freed 124kB init memory.
> >>>>>>>
> >>>>>>> ============================================
> >>>>>>>
> >>>>>>> [root@b52 ~]# xenpm get-cpuidle-states
> >>>>>>> Max C-state: C7
> >>>>>>>
> >>>>>>> cpu id : 0
> >>>>>>> total C-states : 0
> >>>>>>> idle time(ms) : 0
> >>>>>>>
> >>>>>>> cpu id : 1
> >>>>>>> total C-states : 0
> >>>>>>> idle time(ms) : 0
> >>>>>>>
> >>>>>>> cpu id : 2
> >>>>>>> total C-states : 0
> >>>>>>> idle time(ms) : 0
> >>>>>>>
> >>>>>>> cpu id : 3
> >>>>>>> total C-states : 0
> >>>>>>> idle time(ms) : 0
> >>>>>>>
> >>>>>>> cpu id : 4
> >>>>>>> total C-states : 0
> >>>>>>> idle time(ms) : 0
> >>>>>>>
> >>>>>>> cpu id : 5
> >>>>>>> total C-states : 0
> >>>>>>> idle time(ms) : 0
> >>>>>>>
> >>>>>>> cpu id : 6
> >>>>>>> total C-states : 0
> >>>>>>> idle time(ms) : 0
> >>>>>>>
> >>>>>>> cpu id : 7
> >>>>>>> total C-states : 0
> >>>>>>> idle time(ms) : 0
> >>>>>>>
> >>>>>>> [root@b52 ~]# xenpm get-cpufreq-states
> >>>>>>> [root@b52 ~]# xenpm get-cpufreq-para
> >>>>>>> [CPU0] failed to get cpufreq parameter
> >>>>>>> [CPU1] failed to get cpufreq parameter
> >>>>>>> [CPU2] failed to get cpufreq parameter
> >>>>>>> [CPU3] failed to get cpufreq parameter
> >>>>>>> [CPU4] failed to get cpufreq parameter
> >>>>>>> [CPU5] failed to get cpufreq parameter
> >>>>>>> [CPU6] failed to get cpufreq parameter
> >>>>>>> [CPU7] failed to get cpufreq parameter
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>>
> >>>>>>> Mike
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Xen-devel mailing list
> >>>>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
> >>>>>> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home