Messages in this thread | | | Date | Wed, 13 Apr 2022 10:31:20 +0200 | Subject | Re: [PATCH] KVM: x86: Don't snapshot "max" TSC if host TSC is constant | From | Paolo Bonzini <> |
| |
On 4/12/22 19:38, Anton Romanov wrote: >> Queued, but I'd rather have a subject that calls out that max_tsc_khz >> needs a replacement at vCPU creation time. In fact, the real change >> (and bug, and fix) is in kvm_arch_vcpu_create(), while the subject >> mentions only the change in kvm_timer_init(). >> >> What do you think of "KVM: x86: Use current rather than max TSC >> frequency if it is constant"? > > Ping. This said "queued" but I don't think this ever landed. > What's the status of this? > Paolo, does this need more work?
The features in my second pull request were rejected by Linus so they will be in 5.19. I'm going to open kvm/next today and the patches will be there.
Unfortunately he hasn't replied to my rebuttal at https://lore.kernel.org/kvm/30ffdecc-6ecd-5194-14ec-40e8b818889a@redhat.com/#t so I have no idea what his opinion is. I'll try to get more stuff in early for the next releases.
Paolo
| |