Re: SpeedStep in DomUs?

Subject: Re: SpeedStep in DomUs?
From: Stefan GroÃ <kong%kong74.org@localhost>
Date: Sun, 11 Jul 2010 13:24:21 +0200

Ok, thanks for the Tip. That didn't work that easy, and i think i found
the reason here: http://wiki.xensource.com/xenwiki/xenpm They say:
"Domain0 based cpufreq has one limitations, i.e. domain0 VCPU number
must be the same as the number of physical CPUs, and the domain0 VCPU
must be pinned to physical CPU"
I didn't try to set that, because the same page talks about
frequency-control with xen, and i thought that should be more robust, so
i tryed to set up that first.
But that doesn't seem to work for me too, although i enabled support for
deep c-states in the bios, and also support for est (Enhanced Speed
Step). I attached some Info: output of "xm dmesg" and of "xenpm
get-cpufreq-states". Can anyone help me on that?
And the second question is: If i can't get the xen-throttling, how do i
setup my dom0 to meet the requirenments of the limitation? (that's
really a newbie-question, what files to edit how? Till now i don't have
a setup-file for dom0 - is it boot-options?)

s.

On 05/22/10 14:31, Jean-Yves Migeon wrote:
> On 22.05.2010 11:11, Stefan GroÃ wrote:
>> Hello,
>> i wonder if i can use SpeedSteping e.g. through the estd-daemon in
>> paravirtualized NetBSD-domUs on a NetBSD-dom0. The cpus are able to do
>> so and it works with a native NetBSD install.
> 
> ACPI/power control is mostly under control of the dom0 and Xen. I don't
> think you can/should be able to mess with power control features within
> a domU. This requires privileges, as you could potentially cause DoS by
> simply reducing frequency. BTW, domUs have no knowledge of the
> scheduling of other domains, so it cannot take good decisions regarding
> power saving.
> 
> For the rest, to enable speedstep control within dom0, boot by passing
> 'cpufreq=dom0-kernel' to Xen. You may have clock skew in the long run,
> so ensure you control drift (through ntp, for example).
> 
> menu=Boot Xen:load /netbsd-xen0 console=pc;multiboot
> /usr/pkg/xen3-kernel/xen.gz dom0_mem=XXXM cpufreq=dom0-kernel
>

Output from xm dmesg:
---------------------
 __  __            _____  _____  ____  
 \ \/ /___ _ __   |___ / |___ / |___ \ 
  \  // _ \ '_ \    |_ \   |_ \   __) |
  /  \  __/ | | |  ___) | ___) | / __/ 
 /_/\_\___|_| |_| |____(_)____(_)_____|
                                       
(XEN) Xen version 3.3.2 (root@) (gcc version 4.1.3 20080704 prerelease (NetBSD 
nb2 20081120)) Sat Jul 10 12:10:00 CEST 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: dom0_mem=2048M cpufreq=xen cpuidle
(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 4 MBR signatures
(XEN)  Found 4 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009d000 (usable)
(XEN)  000000000009d000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000009f91a000 (usable)
(XEN)  000000009f91a000 - 000000009f9d1000 (ACPI NVS)
(XEN)  000000009f9d1000 - 000000009fa32000 (usable)
(XEN)  000000009fa32000 - 000000009fa9a000 (reserved)
(XEN)  000000009fa9a000 - 000000009fad4000 (usable)
(XEN)  000000009fad4000 - 000000009fb1a000 (ACPI NVS)
(XEN)  000000009fb1a000 - 000000009fb27000 (usable)
(XEN)  000000009fb27000 - 000000009fb3a000 (ACPI data)
(XEN)  000000009fb3a000 - 000000009fc00000 (usable)
(XEN)  000000009fc00000 - 00000000b0000000 (reserved)
(XEN)  00000000ffc00000 - 00000000ffc0c000 (reserved)
(XEN)  0000000100000000 - 0000000260000000 (usable)
(XEN) System RAM: 8186MB (8382612kB)
(XEN) ACPI: RSDP 000F0410, 0024 (r2 INTEL )
(XEN) ACPI: XSDT 9FB39120, 007C (r1 INTEL  S5000PSL        0 INTL  1000013)
(XEN) ACPI: FACP 9FB37000, 00F4 (r3 INTEL  S5000PSL        0 INTL  1000013)
(XEN) ACPI: DSDT 9FB30000, 5809 (r2 INTEL  S5000PSL        1 INTL  1000013)
(XEN) ACPI: FACS 9FAD4000, 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, 0193 (r2  INTEL IPMI         4000 INTL 20060317)
(XEN) ACPI: SSDT 9FB2B000, 02D4 (r2  INTEL CST          4000 INTL 20060317)
(XEN) ACPI: HEST 9FB2A000, 00A8 (r1 INTEL  S5000PSL        1 INTL        1)
(XEN) ACPI: BERT 9FB29000, 0030 (r1 INTEL  S5000PSL        1 INTL        1)
(XEN) ACPI: ERST 9FB28000, 0230 (r1 INTEL  S5000PSL        1 INTL        1)
(XEN) ACPI: EINJ 9FB27000, 0130 (r1 INTEL  S5000PSL        1 INTL        1)
(XEN) Xen heap: 14MB (14584kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #6 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) Processor #7 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47
(XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 1995.081 MHz processor.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC TPR shadow
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz stepping 06
(XEN) Booting processor 1/6 eip 8c000
(XEN) CPU1: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz stepping 06
(XEN) Booting processor 2/1 eip 8c000
(XEN) CPU2: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz stepping 06
(XEN) Booting processor 3/7 eip 8c000
(XEN) CPU3: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz stepping 06
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 4 CPUs
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80100000 -> 0xffffffff80ca1bc0
(XEN)  Dom0 symbol map 0xffffffff80ca1bc0 -> 0xffffffff80da0828
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000256000000->0000000258000000 (516096 pages to be 
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80100000->ffffffff80da0828
(XEN)  Init. ramdisk: ffffffff80da1000->ffffffff80da1000
(XEN)  Phys-Mach map: ffffffff80da1000->ffffffff811a1000
(XEN)  Start info:    ffffffff811a1000->ffffffff811a14a4
(XEN)  Page tables:   ffffffff811a2000->ffffffff811af000
(XEN)  Boot stack:    ffffffff811af000->ffffffff811b0000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81400000
(XEN)  ENTRY ADDRESS: ffffffff80100000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM: 
............................................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(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 104kB init memory.
(XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000102f7, new_entry=00010900
(XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector f7
(XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900
(XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=16, old_irq=-1, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000102f7, new_entry=0001a900
(XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector f7
(XEN) ioapic_guest_write: apic=0, pin=22, old_irq=-1, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000102e3, new_entry=0001a900
(XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector e3
(XEN) ioapic_guest_write: apic=0, pin=23, old_irq=-1, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000102e3, new_entry=0001a900
(XEN) ioapic_guest_write: Special delivery mode 2 with non-zero vector e3

Output from xenpm get-cpufreq-states:
-------------------------------------
cpu id               : 0
total C-states       : 0
idle time(ms)        : 872401

cpu id               : 1
total C-states       : 0
idle time(ms)        : 675515

cpu id               : 2
total C-states       : 0
idle time(ms)        : 680569

cpu id               : 3
total C-states       : 0
idle time(ms)        : 680480

[CPU0] failed to get max P-state
[CPU1] failed to get max P-state
[CPU2] failed to get max P-state
[CPU3] failed to get max P-state

Follow-Ups:
- Re: SpeedStep in DomUs?
  - From: Jean-Yves Migeon

References:
- SpeedStep in DomUs?
  - From: Stefan GroÃ
- Re: SpeedStep in DomUs?
  - From: Jean-Yves Migeon

Prev by Date: Re: Balloon driver.
Next by Date: Re: SpeedStep in DomUs?
Previous by Thread: Re: SpeedStep in DomUs?
Next by Thread: Re: SpeedStep in DomUs?
Indexes:

Home | Main Index | Thread Index | Old Index