From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>
Cc: Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
Michael Kelley <mikelley@microsoft.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/7] KVM: x86: Hyper-V invariant TSC control feature
Date: Thu, 13 Oct 2022 11:58:42 +0200 [thread overview]
Message-ID: <20221013095849.705943-1-vkuznets@redhat.com> (raw)
Changes since v4:
- s,HV_INVARIANT_TSC_EXPOSED,HV_EXPOSE_INVARIANT_TSC, [Michael]
- Add Michael's R-b to PATCH1
- Use 'KVM-only' instead of 'scattered' in PATCH2's subject [Sean, Jim]
- Do not set CPUID_8000_0007_EDX to 'NCAPINTS + 1' explicitly [Sean]
- Use the opportunity and switch to 'true'/'false' for 'msr->write'/
'msr->fault_exepected' in 'hyperv_features' test [Sean]
- Fix HVCALL_NOTIFY_LONG_SPIN_WAIT test breakage by setting
HYPERV_CPUID_ENLIGHTMENT_INFO.EBX.
- "KVM: selftests: Test that values written to Hyper-V MSRs are
preserved" patch added [Sean]
Original description:
Normally, genuine Hyper-V doesn't expose architectural invariant TSC
(CPUID.80000007H:EDX[8]) to its guests by default. A special PV MSR
(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x40000118) and corresponding CPUID
feature bit (CPUID.0x40000003.EAX[15]) were introduced. When bit 0 of the
PV MSR is set, invariant TSC bit starts to show up in CPUID. When the
feature is exposed to Hyper-V guests, reenlightenment becomes unneeded.
Note: strictly speaking, KVM doesn't have to have the feature as exposing
raw invariant TSC bit (CPUID.80000007H:EDX[8]) also seems to work for
modern Windows versions. The feature is, however, tiny and straitforward
and gives additional flexibility so why not.
Vitaly Kuznetsov (7):
x86/hyperv: Add HV_EXPOSE_INVARIANT_TSC define
KVM: x86: Add a KVM-only leaf for CPUID_8000_0007_EDX
KVM: x86: Hyper-V invariant TSC control
KVM: selftests: Rename 'msr->available' to 'msr->fault_exepected' in
hyperv_features test
KVM: selftests: Convert hyperv_features test to using
KVM_X86_CPU_FEATURE()
KVM: selftests: Test that values written to Hyper-V MSRs are preserved
KVM: selftests: Test Hyper-V invariant TSC control
arch/x86/include/asm/hyperv-tlfs.h | 3 +
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kernel/cpu/mshyperv.c | 2 +-
arch/x86/kvm/cpuid.c | 11 +-
arch/x86/kvm/hyperv.c | 19 +
arch/x86/kvm/hyperv.h | 27 ++
arch/x86/kvm/reverse_cpuid.h | 7 +
arch/x86/kvm/x86.c | 4 +-
.../selftests/kvm/include/x86_64/hyperv.h | 144 +++++---
.../selftests/kvm/include/x86_64/processor.h | 1 +
.../selftests/kvm/x86_64/hyperv_features.c | 330 +++++++++++-------
11 files changed, 366 insertions(+), 183 deletions(-)
--
2.37.3
next reply other threads:[~2022-10-13 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 9:58 Vitaly Kuznetsov [this message]
2022-10-13 9:58 ` [PATCH v5 1/7] x86/hyperv: Add HV_EXPOSE_INVARIANT_TSC define Vitaly Kuznetsov
2022-10-13 9:58 ` [PATCH v5 2/7] KVM: x86: Add a KVM-only leaf for CPUID_8000_0007_EDX Vitaly Kuznetsov
2022-10-13 9:58 ` [PATCH v5 3/7] KVM: x86: Hyper-V invariant TSC control Vitaly Kuznetsov
2022-10-13 9:58 ` [PATCH v5 4/7] KVM: selftests: Rename 'msr->available' to 'msr->fault_exepected' in hyperv_features test Vitaly Kuznetsov
2022-10-13 9:58 ` [PATCH v5 5/7] KVM: selftests: Convert hyperv_features test to using KVM_X86_CPU_FEATURE() Vitaly Kuznetsov
2022-10-13 9:58 ` [PATCH v5 6/7] KVM: selftests: Test that values written to Hyper-V MSRs are preserved Vitaly Kuznetsov
2022-10-13 9:58 ` [PATCH v5 7/7] KVM: selftests: Test Hyper-V invariant TSC control Vitaly Kuznetsov
2022-10-14 20:04 ` [PATCH v5 0/7] KVM: x86: Hyper-V invariant TSC control feature Sean Christopherson
2022-11-22 15:43 ` Vitaly Kuznetsov
2022-12-24 11:04 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221013095849.705943-1-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=wanpengli@tencent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®