I'm having the same issue with Ubuntu 20.04, linux 5.4.0-31-generic:
user@linux:~$ sudo perf stat -e
cpu/event=0x28,umask=0x18,name=core_power_lvl1_turbo_license/,cpu/event=0x28,umask=0x20,name=core_power_lvl2_turbo_license/,cpu/event=0x28,umask=0x40,name=core_power_throttle/,cycles
-a -I 1000 sleep 10
# time counts unit events
1.000170047 1.861 core_power_lvl1_turbo_license
1.000170047 284 core_power_lvl2_turbo_license
1.000170047 103.012 core_power_throttle
1.000170047 26.525.939 cycles
2.000358208 2.873 core_power_lvl1_turbo_license
2.000358208 411 core_power_lvl2_turbo_license
2.000358208 120.125 core_power_throttle
2.000358208 35.270.662 cycles
3.000529648 2.995 core_power_lvl1_turbo_license
3.000529648 325 core_power_lvl2_turbo_license
3.000529648 103.505 core_power_throttle
3.000529648 49.564.376 cycles
4.000701689 2.519 core_power_lvl1_turbo_license
4.000701689 354 core_power_lvl2_turbo_license
4.000701689 107.696 core_power_throttle
4.000701689 32.302.985 cycles
5.000874532 2.758 core_power_lvl1_turbo_license
5.000874532 366 core_power_lvl2_turbo_license
5.000874532 141.070 core_power_throttle
5.000874532 36.180.579 cycles
6.001046915 2.626 core_power_lvl1_turbo_license
6.001046915 370 core_power_lvl2_turbo_license
6.001046915 116.084 core_power_throttle
6.001046915 38.366.890 cycles
7.001218040 26.266 core_power_lvl1_turbo_license
7.001218040 418 core_power_lvl2_turbo_license
7.001218040 128.776 core_power_throttle
7.001218040 1.201.403.076 cycles
8.001399922 2.625 core_power_lvl1_turbo_license
8.001399922 410 core_power_lvl2_turbo_license
8.001399922 106.382 core_power_throttle
8.001399922 33.190.255 cycles
9.001568738 2.781 core_power_lvl1_turbo_license
9.001568738 384 core_power_lvl2_turbo_license
9.001568738 138.116 core_power_throttle
9.001568738 35.559.397 cycles
10.000447616 4.056 core_power_lvl1_turbo_license
10.000447616 632 core_power_lvl2_turbo_license
10.000447616 201.168 core_power_throttle
10.000447616 41.275.834 cycles
Are there any updates?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1727136
Title:
[GLIBC] Fix glibc AVX frequency problems
Status in Linux:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
Various glibc versions use AVX512 or AVX incorrectly in memcpy/memset or use
AVX unintentionally due to branch mispredictions. On SKX using AVX can lower
the frequency by several bins.
There was a decision to not use AVX in memcpy/memset to avoid these problems
for legacy code.
glibc mainline has been fixed. The actual state per version depends on the
version, and what backports it has applied.
See the attachment for the fix status for several glibc versions. Need to
figure out for each supported glibc release if they are affected, and submit
backports of the fixes.
How to test:
Non AVX test code like compiles should not report any LVL1,2 AVX licenses with
perf stat -e
cpu/event=0x28,umask=0x18,name=core_power_lvl1_turbo_license/,cpu/event=0x28,umask=0x20,name=core_power_lvl2_turbo_license/,cpu/event=0x28,umask=0x40,name=core_power_throttle/,cycles
-a -I 1000 sleep 10
17.10 also hit this issue, when testing, need run some others application.
For example, building kernel.
16.04 hit the issue.
Target Release: 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1727136/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
