On 6/1/22 10:54, Durrant, Paul wrote:
That is exactly the case. This is not 'some hare-brained money
scheme'; there is genuine concern that moving a VM from old h/w to
new h/w may cause it to run 'too fast', breaking any such calibration
done by the guest OS/application. I also don't have any real-world
examples, but bugs may well be reported and having a lever to address
them is IMO a good idea. However, I also agree with Paolo that KVM
doesn't really need to be doing this when the VMM could do the job
using cpufreq, so we'll pursue that option instead. (FWIW the reason
for involving KVM was to do the freq adjustment right before entering
the guest and then remove the cap right after VMEXIT).
But if so, you still would submit the full feature, wouldn't you?
Paul, thanks for chiming in, and sorry for leaving you out of the list
of people that can help Jack with his upstreaming efforts. :)
Paolo
