search for: cpu_freq

...e the command line >cannot grow arbitrarily large. Agree then. We''ll send out a fix. > >>>In any case there is an open question for me as to how current status >>>is being reported to the user (at least in Dom0) on the current CPU >>>frequency in use when CPU_FREQ is configured off (and I have to >> >>If CPU_FREQ is off, error is returned when user tries to query >>cpufreq information from Xen. > >You mean when (in Xen) control is set to FREQCTL_dom0_kernel. But >my question was how this works when CPU_FREQ is configured off >in...

...ather than through the startup info. I think this should be adjusted before 3.3 gets frozen. Besides that I continue to wonder what significance the support for Dom0-controlled cpufreq handling has now that Xen has the ability to handle that. I ask this not the least because so far we disabled the CPU_FREQ config option in our kernels, partly because of the unknown status of all of the different low level drivers (powernow-k8 supposedly works, acpi-cpufreq apparently might work, too, but most others I''m pretty unclear about), but also because of the massive (and afaict not upstream) changes...

Dear libvirt experts, I can not instantiate even a simple machine when using the 'vbox' hypervisor: s14% virt-install --connect=vbox:///session --virt-type vbox --name vtest --memory 500 ERROR cannot obtain CPU freq: No such file or directory s14% virsh -c vbox:///session błąd: cannot obtain CPU freq: No such file or directory (1) How to fix this error? The VirtualBox driver seems

To my surprise, c/s 8888 enables CPU_FREQ for x86-64 rather than disabling it for i386. Did anyone at your end actually test that if enabled this at least builds properly now? Not to mention that of course this also should work... If I remember right, the main reason for posting a patch to disable it on 32-bits (similar to how it was on 64...

...OM0_PHYSINFO; - op.interface_version = DOM0_INTERFACE_VERSION; - - ret = xc_dom0_op(xc_handle, &op); + ret = xc_physinfo(xc_handle, &physinfo); if ( ret != 0 ) { @@ -460,12 +457,12 @@ unsigned int get_num_cpus(void) } xc_interface_close(xc_handle); - opts.cpu_freq = (double)op.u.physinfo.cpu_khz/1000.0; - - return (op.u.physinfo.threads_per_core * - op.u.physinfo.cores_per_socket * - op.u.physinfo.sockets_per_node * - op.u.physinfo.nr_nodes); + opts.cpu_freq = (double)physinfo.cpu_khz/1000.0; + + return (physinfo.thr...

Could anyone summarize what the support status of cpu frequency changes is at present. I don''t seem to recall generic changes to the hpyervisor in that respect, but the linux tree has fairly extensive changes to the powernow-k8 driver (which would make sense to me only if all other cpufreq drivers are fully supported now, too). Thanks, Jan

...39;total_memory''] / 1024 diff -r 51045f276c90 tools/xenmon/xenbaked.c --- a/tools/xenmon/xenbaked.c Mon Jul 31 10:48:48 2006 -0500 +++ b/tools/xenmon/xenbaked.c Mon Jul 31 10:49:10 2006 -0500 @@ -462,10 +462,7 @@ unsigned int get_num_cpus(void) xc_interface_close(xc_handle); opts.cpu_freq = (double)op.u.physinfo.cpu_khz/1000.0; - return (op.u.physinfo.threads_per_core * - op.u.physinfo.cores_per_socket * - op.u.physinfo.sockets_per_node * - op.u.physinfo.nr_nodes); + return op.u.physinfo.nr_cpus; } diff -r 51045f276c90 tools/xenstat/libx...

...ESR value after enabling vector: 00000000 (XEN) Using local APIC timer interrupts. (XEN) Calibrating APIC timer for CPU0... (XEN) ..... CPU speed is 1197.8705 MHz. (XEN) ..... Bus speed is 69.3984 MHz. (XEN) ..... bus_scale = 0x00004711 (XEN) Time init: (XEN) .... System Time: 1451424ns (XEN) .... cpu_freq: 00000000:47666D94 (XEN) .... scale: 00000001:AB6A9983 (XEN) .... Wall Clock: 1104628571s 10000us (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfd9a0, last bus=1 (XEN) PCI: Using configuration type 1 (XEN) PCI: Probing PCI hardware (XEN) PCI: Probing PCI hardware (bus 00) (XEN) PCI: Using...

...IC timer for CPU0... -(XEN) ..... CPU speed is 451.0230 MHz. -(XEN) ..... Bus speed is 100.2271 MHz. +(XEN) ..... CPU clock speed is 451.0303 MHz. +(XEN) ..... host bus clock speed is 100.2288 MHz. (XEN) ..... bus_scale = 0x000066A2 (XEN) Time init: -(XEN) .... System Time: 12217304ns -(XEN) .... cpu_freq: 00000000:1AE22E48 -(XEN) .... scale: 00000002:3796C7A7 -(XEN) .... Wall Clock: 1114087225s 40000us +(XEN) .... System Time: 80262159ns +(XEN) .... cpu_freq: 00000000:1AE24040 +(XEN) .... scale: 00000002:37954C49 +(XEN) .... Wall Clock: 1114087099s 0us (XEN) PCI: PCI BIOS revis...

...(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0 (XEN) Using local APIC timer interrupts. (XEN) Calibrating APIC timer for CPU0... (XEN) ..... CPU speed is 2600.0929 MHz. (XEN) ..... Bus speed is 200.0070 MHz. (XEN) ..... bus_scale = 0x0000CCD7 (XEN) Time init: (XEN) .... System Time: 20000524ns (XEN) .... cpu_freq: 00000000:9AFB7DF0 (XEN) .... scale: 00000001:89D1E7D3 (XEN) .... Wall Clock: 1123496577s 180000us (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=3 (XEN) PCI: Using configuration type 1 (XEN) PCI: Probing PCI hardware (XEN) PCI: Probing PCI hardware (bus 00) (XEN) PCI: Ignor...

Hi, while testing some APERF/MPERF semantics I discovered that this feature is enabled in Xen Dom0, but is not reliable. The Linux kernel''s scheduler uses this feature if it sees the CPUID bit, leading to costly RDMSR traps (a few 100,000s during a kernel compile) and bogus values due to VCPU migration during the measurement. The attached patch explicitly disables this CPU capability

...2 idle time(ms) : 73264 C0 : transition [00000000000000000000] residency [00000000000000000000 ms] C1 : transition [00000000000000025505] residency [00000000000000000000 ms] (repeats for all cores) However, CPU_FREQ depends on PROCESSOR_EXTERNAL_CONTROL being set to ''n''. There doesn''t seem to be a way to enable/disable CONFIG_PROCESSOR_EXTERNAL_CONTROL from menuconfig. I therefore manually twiddled that bits in .config and enabled CPU_FREQ and CPU_FREQ_TABLE (plus the performance gov...

...cache: 16K (XEN) CPU: L2 cache: 1024K (XEN) CPU: Physical Processor ID: 0 (XEN) CPUU 3.60GHz stepping 01 (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1 (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Time init: (XEN) .... cpu_freq: 00000000:D6987764 (XEN) .... scale: 00000001:1C6B619C (XEN) .... Wall Clock: 1118847138s 160000us (XEN) Brought up 4 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80100000...

...or: 00000040 ESR value after enabling vector: 00000000 Using local APIC timer interrupts. Calibrating APIC timer for CPU0... ..... CPU speed is 1129.5684 MHz. ..... Bus speed is 132.8903 MHz. ..... bus_scale = 0x00008814 ACT: Initialising Accurate timers Time init: .... System Time: 11843241ns .... cpu_freq: 00000000:43541940 .... scale: 00000001:C5438A0E .... Wall Clock: 1092158215s 0us Start schedulers PCI: PCI BIOS revision 2.10 entry at 0xfbfee, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware Transparent bridge - PCI device 8086:244e PCI: Using IRQ router PIIX [8086/...

Testing on an 8-node 128-way NUMA machine has exposed a problem with Xen''s nr_cpus calculation. In this case, since Xen cuts off recognized CPUs at 32, the machine appears to have 16 CPUs on the first and second nodes and none on the remaining nodes. Given this asymmetry, the calculation of sockets_per_node (which is later used to calculate nr_cpus) is incorrect:

...cal APIC timer interrupts. (XEN) Calibrating APIC timer for CPU0... (XEN) ..... CPU speed is 2392.1847 MHz. (XEN) ..... Bus speed is 99.6742 MHz. (XEN) ..... bus_scale = 0x0000661 (XEN) checking TSC synchronization across CPUs: passed. (XEN) Time init: (XEN) .... System Time: 12936158ns (XEN) .... cpu_freq: 00000000:8E981F50 (XEN) .... scale: 00000001:AC08AA5D (XEN) .... Wall Clock: 1098363022s 160000us (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfd81c, last bus=2 (XEN) PCI: Using configuration type 1 (XEN) PCI: Probing PCI hardware (XEN) PCI: Probing PCI hardware (bus 00) (XEN) PCI: Igno...

...that do this and use them within the >> cpufreq-xen-scaling-driver but that sounds icky. > > Indeed. > >> 2). Upload the power management information up to the hypervisor. > > Which doesn''t require cpufreq drivers at all (in non-pv-ops we simply > suppress the CPU_FREQ config option when XEN is set). Heh. > > Jan > >

Dear list, I''m trying to get Xen working on a P3-600E with 320 MB RAM. (256+64) It has suse linux 9.1 installed on it, and I tried to get xen running with both the binary download from the xen pages and the suse xen packages mentioned on this list some days ago. Both ''install packages/kernels'' lead to the same error: (XEN) Not enough memory for DOM0 memory

I have a 2 way machine. Soliciting folks opinion on whether it makes sense to smp enable DOM0 so that IO handling can be balanced over both CPU''s... Opinions? Thanks, Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...2 cache: 1024K (XEN) CPU: Physical Processor ID: 3 (XEN) CPU3: Intel(R) Xeon(TM) CPU 3.20GHz stepping 01 (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1 (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Time init: (XEN) .... cpu_freq: 00000000:BE46EF60 (XEN) .... scale: 00000001:40C515C9 (XEN) .... Wall Clock: 1121013264s 120000us (XEN) Brought up 4 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,LOADE...