On 28.01.2020 16:56, PGNet Dev wrote:
> ( I'd already posted this at xen-users; no traction to date )
>
> I'm running linux kernel
>
> lsb_release -rd
> Description: openSUSE Leap 15.1
> Release: 15.1
>
> uname -rm
> 5.4.14-24.gfc4ea7a-default x86_64
>
> dmesg | grep DMI:
> [ 0.000000] DMI: Supermicro X10SAT/X10SAT, BIOS 3.0
> 05/26/2015
>
> cat /proc/cpuinfo | grep "model name" | head -n 1
> model name : Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz
>
> kernel & xen are pkg-installed from my KernelStable and Virtualization-Xen
> repos @ OBS.
>
> BIOS *is* setup for max cstate support.
> Xeon E3-1220 does support intel_pstate driver.
>
> Testing first,
>
> (1) boot, NO XEN
>
> pstate driver's init'd
>
> dmesg | egrep -i "intel_pstate"
> [ 6.132964] intel_pstate: Intel P-state driver initializing
>
> pstate/cstate info
>
> cat /sys/module/intel_idle/parameters/max_cstate
> 9
>
> cd /sys/devices/system/cpu/cpu0/cpuidle
> for state in state{0..9}
> do echo c-$state `cat $state/name` `cat $state/latency`
> done
> c-state0 POLL 0
> c-state1 C1 2
> c-state2 C1E 10
> c-state3 C3 33
> c-state4 C6 133
> c-state5 C7s 166
> cat: state6/name: No such file or directory
> cat: state6/latency: No such file or directory
> c-state6
> cat: state7/name: No such file or directory
> cat: state7/latency: No such file or directory
> c-state7
> cat: state8/name: No such file or directory
> cat: state8/latency: No such file or directory
> c-state8
> cat: state9/name: No such file or directory
> cat: state9/latency: No such file or directory
> c-state9
>
>
> cpufreq scaling info's available,
>
> cpupower frequency-info
> analyzing CPU 0:
> driver: intel_pstate
> CPUs which run at the same hardware frequency: 0
> CPUs which need to have their frequency coordinated by
> software: 0
> maximum transition latency: Cannot determine or is not
> supported.
> hardware limits: 800 MHz - 3.50 GHz
> available cpufreq governors: performance powersave
> current policy: frequency should be within 800 MHz and 3.50
> GHz.
> The governor "powersave" may decide which
> speed to use
> within this range.
> current CPU frequency: Unable to call hardware
> current CPU frequency: 799 MHz (asserted by call to kernel)
> boost state support:
> Supported: yes
> Active: yes
>
> & scaling is in effect,
>
> cat /proc/cpuinfo | grep MHz
> cpu MHz : 798.106
> cpu MHz : 798.129
> cpu MHz : 798.964
> cpu MHz : 798.154
>
> (2) boot, WITH Xen 4.13
>
> rpm -qa | grep -i xen | sort
> grub2-x86_64-xen-2.04-lp151.6.5.noarch
> xen-4.13.0_04-lp151.688.2.x86_64
> xen-libs-4.13.0_04-lp151.688.2.x86_64
> xen-tools-4.13.0_04-lp151.688.2.x86_64
>
> Xen cmd line includes,
>
> grep options= /boot/grub2/xen-4.13.0_04-lp151.688.cfg
> [config.1]
> options=dom0=pvh dom0-iommu=map-reserved
> dom0_mem=4016M,max:4096M dom0_max_vcpus=4 cpufreq=xen cpuidle ucode=scan ...
>
> intel_pstate support is now DISABLED for this cpu
>
> xl dmesg | grep pstate
> [ 6.851121] intel_pstate: CPU model not supported
>
>
> c-states report,
>
> xenpm get-cpuidle-states 0
>
> All C-states allowed
>
> cpu id : 0
> total C-states : 6
> idle time(ms) : 45780911
> C0 : transition [ 3204855]
> residency [ 160769 ms]
> C1 : transition [ 9204]
> residency [ 1018 ms]
> C2 : transition [ 10181]
> residency [ 2848 ms]
> C3 : transition [ 22784]
> residency [ 17236 ms]
> C4 : transition [ 7181]
> residency [ 11793 ms]
> C5 : transition [ 3155504]
> residency [ 45668846 ms]
> pc2 : [ 1685 ms]
> pc3 : [ 30695 ms]
> cc3 : [ 16858 ms]
> cc6 : [ 11640 ms]
> cc7 : [ 45602872 ms]
>
> NO cpupower frequency-info is available
>
> cpupower frequency-info
> analyzing CPU 0:
> no or unknown cpufreq driver is active on this CPU
> CPUs which run at the same hardware frequency: Not Available
> CPUs which need to have their frequency coordinated by
> software: Not Available
> maximum transition latency: Cannot determine or is not
> supported.
> Not Available
> available cpufreq governors: Not Available
> Unable to determine current policy
> current CPU frequency: Unable to call hardware
> current CPU frequency: Unable to call to kernel
> boost state support:
> Supported: no
> Active: no
>
> and scaling is NOT in effect
>
> cat /proc/cpuinfo | grep MHz
> cpu MHz : 3092.828
> cpu MHz : 3092.828
> cpu MHz : 3092.828
> cpu MHz : 3092.828
>
> attempt to add acpi-cpufreq module fails
>
> lsmod | grep acpi-cpufreq
> (empty)
> find /lib/modules/ | grep acpi-cpu
>
> /lib/modules/5.4.14-24.gfc4ea7a-default/kernel/drivers/cpufreq/acpi-cpufreq.ko
> modprobe acpi-cpufreq
> modprobe: ERROR: could not insert 'acpi_cpufreq': No such device
> insmod
> /lib/modules/5.4.14-24.gfc4ea7a-default/kernel/drivers/cpufreq/acpi-cpufreq.ko
> insmod: ERROR: could not insert module
> /lib/modules/5.4.14-24.gfc4ea7a-default/kernel/drivers/cpufreq/acpi-cpufreq.ko:
> No such device
>
> Is this bug, or config?
Neither (at least as far as Xen and the kernel are concerned). The
management of this lives in Xen, and hence the kernel doesn't know
(and kernel drivers don't get involved). The various user space
tools would of course be nice if they knew how to get at the
relevant data, but that's a separate issue. Until then xenpm is
what shows you some of the relevant data (and if more is needed,
such could be discussed on xen-devel). Just like you've used
"xenpm get-cpuidle-states 0" to get C-state information, you should
be able to obtain P-state one via "xenpm get-cpufreq-states 0".
Jan
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
