On Tue, Oct 20, 2020 at 05:44:38PM +0200, Redha Gouicem wrote: > > The first patch of the series is not specific to scheduling. It allows us > (or anyone else) to use the cpufreq infrastructure at a different sampling > rate without compromising the cpufreq subsystem and applications that > depend on it. It's also completely redudant as the scheduler already reads aperf/mperf on every tick. Clearly you didn't do your homework ;-) > The main idea behind this patch series is to bring to light the frequency > inversion problem that will become more and more prominent with new CPUs > that feature per-core DVFS. The solution proposed is a first idea for > solving this problem that still needs to be tested across more CPUs and > with more applications. Which is why schedutil (the only cpufreq gov anybody should be using) is integrated with the scheduler and closes the loop and tells the CPU about the expected load.
