aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorLadi Prosek <lprosek@redhat.com>2017-07-26 13:32:59 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2017-08-07 15:26:06 +0200
commit72c139bacfa386145d7bbb68c47c8824716153b6 (patch)
tree2661bf0f4153e7e302c78f1a849049db1b15a6e5 /tools/perf/scripts/python/export-to-postgresql.py
parentLinux 4.13-rc4 (diff)
downloadlinux-dev-72c139bacfa386145d7bbb68c47c8824716153b6.tar.xz
linux-dev-72c139bacfa386145d7bbb68c47c8824716153b6.zip
KVM: hyperv: support HV_X64_MSR_TSC_FREQUENCY and HV_X64_MSR_APIC_FREQUENCY
It has been experimentally confirmed that supporting these two MSRs is one of the necessary conditions for nested Hyper-V to use the TSC page. Modern Windows guests are noticeably slower when they fall back to reading timestamps from the HV_X64_MSR_TIME_REF_COUNT MSR instead of using the TSC page. The newly supported MSRs are advertised with the AccessFrequencyRegs partition privilege flag and CPUID.40000003H:EDX[8] "Support for determining timer frequencies is available" (both outside of the scope of this KVM patch). Reviewed-by: Radim Krčmář <rkrcmar@redhat.com> Signed-off-by: Ladi Prosek <lprosek@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions