From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E90DCC4332F for ; Tue, 22 Nov 2022 15:45:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233157AbiKVPpG (ORCPT ); Tue, 22 Nov 2022 10:45:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52630 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232546AbiKVPpD (ORCPT ); Tue, 22 Nov 2022 10:45:03 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E333470A32 for ; Tue, 22 Nov 2022 07:44:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1669131848; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=xWL302xeQNaUeD1XBBbHjOQmICjs58t7c74x1CuLrlw=; b=W2eN7HyqLdqol8AH0AF12gzAlsUbCeON14DTjBmn8Ddkn1SBHcZIyMmcE0Ps43nIOaJ5Yy eKZJ6Q/pTjA2IUhNMJrZ3yqCq7LJJx6ksFPg8/3yAnRcsd2gX4vygpMVJpq0uNvX4O3Lr1 Xhy0fTibIHSmG7ugIh3yrNKZDzqAT6s= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-593-5zV6u3PqNjaX_hcBEfIt1w-1; Tue, 22 Nov 2022 10:43:59 -0500 X-MC-Unique: 5zV6u3PqNjaX_hcBEfIt1w-1 Received: by mail-ed1-f72.google.com with SMTP id w4-20020a05640234c400b004631f8923baso9050384edc.5 for ; Tue, 22 Nov 2022 07:43:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=xWL302xeQNaUeD1XBBbHjOQmICjs58t7c74x1CuLrlw=; b=8SP+rZrW6dyQkGfumr6slyt0//0fwEFkpMmUcRx1s6NShHI3+hm6GloaxtLYvPWTGV 3cpVzwM45HLGr6f0ZJLaB4GkK/oHYJ+UuhwpKJBiqgiVRY8PNpzvSGWBQ9FaBMyKK6kS QDZT0O3VzmE8AWaRQBtAjRtnPyiKgF+vwNOpVlgZALJvorSZ5dtylBJSqdfPPH4tcdNG 7t79B7qtvJgyXNjBmwQNuD/RMk+MzRDvPA6cDonguwgw7zQ9ZmF3oAre/3nHzmNrWxCJ uXfPOESAIkckFqOVTBpduskdUbljyM7aTK76U/Qy6+5mG1zvfjCXV02fRzyeI1zOaeBN DzOQ== X-Gm-Message-State: ANoB5pmJydM5dQMO7O8dYFxt/SdNdofTWCp1ONEq5iDpMv2/B+wgvhXM kj5SrZoJvtcl1oF6baJt4PS0+s7KlV5DXhfIWAV7coPw9eKIJeJ7X5v2H2VQ+7x5BRNVCfeqtpX 9gfDfUe7bEIZkJX0ICCJrn/MJUlHN2A6IpBBxAwQhKIAi1C/uNIcNN5fIaaTlMYZL3p3b9r0TxK 8U X-Received: by 2002:a05:6402:2024:b0:468:f633:9484 with SMTP id ay4-20020a056402202400b00468f6339484mr20729287edb.200.1669131838141; Tue, 22 Nov 2022 07:43:58 -0800 (PST) X-Google-Smtp-Source: AA0mqf6HyiTcH1qadnX+DoTbSf5WrVcbc+T6q+Jo/GX4nTI50Ag4+RR58bqywik7IbUTzuQOnoDUzg== X-Received: by 2002:a05:6402:2024:b0:468:f633:9484 with SMTP id ay4-20020a056402202400b00468f6339484mr20729262edb.200.1669131837911; Tue, 22 Nov 2022 07:43:57 -0800 (PST) Received: from ovpn-194-185.brq.redhat.com (nat-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id fy21-20020a170906b7d500b0077d6f628e14sm6125586ejb.83.2022.11.22.07.43.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Nov 2022 07:43:57 -0800 (PST) From: Vitaly Kuznetsov To: Paolo Bonzini , Sean Christopherson Cc: kvm@vger.kernel.org, Wanpeng Li , Jim Mattson , Michael Kelley , Maxim Levitsky , linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 0/7] KVM: x86: Hyper-V invariant TSC control feature In-Reply-To: References: <20221013095849.705943-1-vkuznets@redhat.com> Date: Tue, 22 Nov 2022 16:43:56 +0100 Message-ID: <87o7szouyr.fsf@ovpn-194-185.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sean Christopherson writes: > On Thu, Oct 13, 2022, Vitaly Kuznetsov wrote: >> 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 > > For the series, in case Paolo ends up grabbing this: > > Reviewed-by: Sean Christopherson > I completely forgot about this one! Any chance it can still be queueed for 6.2? Thanks! -- Vitaly