On Tue, May 31, 2022 at 4:45 PM Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > On Tue, May 31, 2022 at 02:02:36PM +0000, Jack Allister wrote: > > The reasoning behind this is that you may want to run a guest at a > > lower CPU frequency for the purposes of trying to match performance > > parity between a host of an older CPU type to a newer faster one. > > That's quite ludicrus. Also, then it should be the host enforcing the > cpufreq, not the guest. It is a weird usecase indeed, but actually it *is* enforced by the host in Jack's patch. On the other hand doing it by writing random MSRs, with no save and load when the task is scheduled or migrated, will not fly outside Amazon datacenters. The patch also has traces of the Amazon kernel and doesn't apply upstream. Paolo
