On Thu, 2025-09-04 at 04:59 -0700, Sean Christopherson wrote: > > I thought the original problem being solved was that the _guest_ doesn't know the > effective TSC frequency? Userspace can already get the effectively TSC frequency > via KVM_GET_TSC_KHZ, why do we need another uAPI to provide that? (Honest question, > I feel like I'm missing something) I believe that KVM_GET_TSC_KHZ returns what userspace *asked* for the TSC frequency to be (vcpu->arch.virtual_tsc_khz), not what it actually ended up being based on the measured host frequency and the available scaling granularity (vcpu->hw_tsc_khz).
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
