On Wednesday, October 21, 2020 9:47:51 PM CEST Julia Lawall wrote: > > On Wed, 21 Oct 2020, Rafael J. Wysocki wrote: > > > On Wednesday, October 21, 2020 2:42:20 PM CEST Julia Lawall wrote: > > > > > > On Wed, 21 Oct 2020, Peter Zijlstra wrote: > > > > > > > On Wed, Oct 21, 2020 at 01:56:55PM +0200, Julia Lawall wrote: > > > > > Prior to 5.8, my machine was using intel_pstate and had few background > > > > > tasks. Thus the problem wasn't visible in practice. Starting with 5.8 > > > > > the kernel decided that intel_cpufreq would be more appropriate, which > > > > > introduced kworkers every 0.004 seconds on all cores. > > > > > > > > That still doesn't make any sense. Are you running the legacy on-demand > > > > thing or something? > > > > > > > > Rafael, Srinivas, Viresh, how come it defaults to that? > > > > > > The relevant commits are 33aa46f252c7, and 39a188b88332 that fixes a small > > > bug. I have a Intel(R) Xeon(R) CPU E7-8870 v4 @ 2.10GHz that does not > > > have the HWP feature, even though the cores seemed to be able to change > > > their frequencies at the hardware level. > > > > That's in the range of "turbo" P-states (if a P-state above a certain threshold > > is requested by the governor, the processor has a license to choose P-states > > in the range above this threshold by itself). > > Sorry, but I don't understand this answer at all. Well, sorry about that and let me rephrase then. Contemporary CPUs have two ranges of P-states, the so called "guaranteed performance" range and the "turbo" range. In the "guaranteed performance" range the CPU runs in the P-state requested by the governor, unless a higher P-state has been requested for another CPU in its frequency domain (usually covering the entire processor package) , in which case that higher P-state will be used (the effective P-state for all CPUs in the frequency domain is the maximum of all P-states requested for individual CPUs). However, if the governor requests a P-state from the "turbo" range, the processor is not required to take that request literally and the PM unit in it may override the governor's choice and cause the CPU to run in a different P-state (also from the "turbo" range), even if lower P-states have been requested for the other CPUs in the processor package. This is also explained in Documentation/admin-guide/pm/intel_pstate.rst (in the Turbo P-states Support section), in more detail and hopefully more clearly. Cheers!
