On 11/22/2024 12:22 AM, Mingwei Zhang wrote: > Linux guests read IA32_APERF and IA32_MPERF on every scheduler tick > (250 Hz by default) to measure their effective CPU frequency. To avoid > the overhead of intercepting these frequent MSR reads, allow the guest > to read them directly by loading guest values into the hardware MSRs. > > These MSRs are continuously running counters whose values must be > carefully tracked during all vCPU state transitions: > - Guest IA32_APERF advances only during guest execution > - Guest IA32_MPERF advances at the TSC frequency whenever the vCPU is > in C0 state, even when not actively running Any particular reason to treat APERF and MPERF differently? AFAIU, APERF and MPERF architecturally will count when the CPU is in C0 state. MPERF counting at constant frequency and the APERF counting at a variable frequency. Shouldn't we treat APERF and MPERF equal and keep on counting in C0 state and even when "not actively running" ? Can you clarify what do you mean by "not actively running"? Regards Nikunj
