On 1/28/20 8:06 AM, Jan Beulich wrote:
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".
i agree with the _should_ part. unfortunately, it's not currently consistenly responsive, xenpm start 5 Timeout set to 5 seconds Start sampling, waiting for CTRL-C or SIGINT or SIGALARM signal ... Elapsed time (ms): 5000 CPU0: Residency(ms) Avg Res(ms) C0 19 ( 0.40%) 0.03 C1 0 ( 0.00%) 0.00 C2 0 ( 0.00%) 0.00 C3 1 ( 0.02%) 0.22 C4 1 ( 0.02%) 0.59 C5 4978 (99.56%) 8.07 Avg freq -302378336 KHz CPU1: Residency(ms) Avg Res(ms) C0 3 ( 0.08%) 0.03 C1 0 ( 0.00%) 0.00 C2 0 ( 0.00%) 0.00 C3 0 ( 0.00%) 0.00 C4 0 ( 0.00%) 0.00 C5 4996 (99.92%) 35.94 Avg freq -302378336 KHz CPU2: Residency(ms) Avg Res(ms) C0 5000 (100.00%) 5000.27 C1 0 ( 0.00%) 0.00 C2 0 ( 0.00%) 0.00 C3 0 ( 0.00%) 0.00 C4 0 ( 0.00%) 0.00 C5 0 ( 0.00%) 0.00 Avg freq -302378336 KHz CPU3: Residency(ms) Avg Res(ms) C0 5 ( 0.11%) 0.03 C1 0 ( 0.00%) 0.00 C2 0 ( 0.00%) 0.00 C3 0 ( 0.01%) 0.32 C4 0 ( 0.00%) 0.00 C5 4994 (99.88%) 25.48 Avg freq -302378336 KHz Socket 0 PC1 0 ms 0.00% PC2 0 ms 0.00% PC3 0 ms 0.00% Core 0 CPU 0 CC1 0 ms 0.00% CC2 0 ms 0.00% CC3 1 ms 0.02% CC4 0 ms 0.00% CC5 0 ms 0.00% CC6 1 ms 0.02% CC7 4965 ms 99.30% Core 1 CPU 1 CC1 0 ms 0.00% CC2 0 ms 0.00% CC3 0 ms 0.00% CC4 0 ms 0.00% CC5 0 ms 0.00% CC6 0 ms 0.00% CC7 4993 ms 99.86% Core 2 CPU 2 CC1 0 ms 0.00% CC2 0 ms 0.00% CC3 0 ms 0.00% CC4 0 ms 0.00% CC5 0 ms 0.00% CC6 0 ms 0.00% CC7 0 ms 0.00% Core 3 CPU 3 CC1 0 ms 0.00% CC2 0 ms 0.00% CC3 0 ms 0.01% CC4 0 ms 0.00% CC5 0 ms 0.00% CC6 0 ms 0.00% CC7 4989 ms 99.79% xenpm get-cpuidle-states 0 All C-states allowed cpu id : 0 total C-states : 6 idle time(ms) : 46635271 C0 : transition [ 3242686] residency [ 162089 ms] C1 : transition [ 9214] residency [ 1018 ms] C2 : transition [ 10254] residency [ 2871 ms] C3 : transition [ 23259] residency [ 17544 ms] C4 : transition [ 7252] residency [ 11896 ms] C5 : transition [ 3192706] residency [ 46522535 ms] pc2 : [ 1685 ms] pc3 : [ 30695 ms] cc3 : [ 17158 ms] cc6 : [ 11742 ms] cc7 : [ 46455767 ms] but, freq states not so much atm, xenpm get-cpufreq-states (empty) 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 xenpm enable-turbo-mode [CPU0] failed to enable turbo mode (13 - Permission denied) [CPU1] failed to enable turbo mode (13 - Permission denied) [CPU2] failed to enable turbo mode (13 - Permission denied) [CPU3] failed to enable turbo mode (13 - Permission denied) i did find this _old_ (2013) post, Linux 3.4 dom0 kernel error loading xen-acpi-processor: Input/output error https://lists.gt.net/xen/devel/274864 which similarly manifests no cpufreq/turbomode in Dom0, and a fail to load 'xen_acpi_processor' mod unless/until > I found this: http://en.community.dell.com/techcenter/power-cooling/w/wiki/best-practices-... > > So I had to enable "OS Control" for "Power Management" in the Dell server BIOS, > and after that the CPU P-states are available in the ACPI tables, > and xen-acpi-processor driver loads and works OK in the dom0 kernel! Here, on my SuperMicro server, lsmod | grep xen xen_pciback 81920 0 xen_netback 73728 0 xen_blkback 53248 0 xen_gntalloc 20480 0 xen_gntdev 45056 1 xen_evtchn 16384 0 xenfs 16384 1 xen_privcmd 28672 17 xenfs as in that post modprobe -v xen-acpi-processor insmod /lib/modules/5.4.14-25.g170524c-default/kernel/drivers/xen/xen-acpi-processor.ko modprobe: ERROR: could not insert 'xen_acpi_processor': No such device checking the man https://www.supermicro.com/manuals/motherboard/C226/MNL-1544.pdf SM's BIOS doesn't have an identical "OS Control" option. don't recognize what'd be similar ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org