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 0F891C43334 for ; Thu, 7 Jul 2022 10:01:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234442AbiGGKBy (ORCPT ); Thu, 7 Jul 2022 06:01:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59694 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233004AbiGGKBw (ORCPT ); Thu, 7 Jul 2022 06:01:52 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 06C614F19F for ; Thu, 7 Jul 2022 03:01:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1657188111; 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=9SHQnAznbKnOLY1gPlD68a+aIhyQn9db0oXlbPnBHao=; b=DVNIBCl2mlAkqfhTd5KBK9HaK0PwHrCE0IaUBHAMloOMJZ7LQhC8zbBNQvpVf/NhrILIj4 tgVqBQMFoV11ZNviU8BhMgcsG8uICM3LOiLUImjrFMAfJ4wlUuoeVzkzDGJM/k2esKaWRr LoPRYLrEV/P/BSTuPMG2utkDk0eA7gY= Received: from mail-ej1-f71.google.com (mail-ej1-f71.google.com [209.85.218.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-301-wksygBykMZ6bIp4-OZUYTA-1; Thu, 07 Jul 2022 06:01:47 -0400 X-MC-Unique: wksygBykMZ6bIp4-OZUYTA-1 Received: by mail-ej1-f71.google.com with SMTP id gr1-20020a170906e2c100b006fefea3ec0aso4554337ejb.14 for ; Thu, 07 Jul 2022 03:01:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=9SHQnAznbKnOLY1gPlD68a+aIhyQn9db0oXlbPnBHao=; b=1oFxFj3VeUVr+T/YGMk0goumeXBJ+w0NJBMdP0G9oGYvS6zJi3LAwYyS/Oxg71VI00 pHZ7NUHCpoL8fISuTbJ3IyRQAEvG+t44wlon8/T8onMp+RuoUtvpahMXYn9A7tT/JlT+ 2kib84zPaCvyBFoSkLqlzfzB+G3IOaReZOXlfaaQ7BAFg08AGZFrHmoKvkX9DyLMz+Nm j64QHOjrbz1HYsmLVjnwIu5XtY+ibsnty3Xp4m2nprDjW7bn8Oo+mfnB83eAwIMwhIjb hpqh2hiYN5Jv8J7p6MJsmFL0gAGIIYWzdm8/QEOtzRUw9EhpCIbZzWwTLDUR0umsGZXO 7yMA== X-Gm-Message-State: AJIora9unbYPu+fOWLchIUWtHAdo2yLjmFd0YoGDAp1qIkaZBnf2yVnH nWCvqrEg/5q6QEcgzn02110Wp+MFqBknzR5x7f7Uhn664NXCAqizM1dj2OgCEIWa3kmu7FC1MhH bCNWtTFzzMoG/pJfVoS9UZ85+EczZLk7zvWa3BavL6g1g77miNjc2FxyGMmX2LBW5wxqrsvTrxK ZE X-Received: by 2002:a05:6402:2708:b0:435:da6f:3272 with SMTP id y8-20020a056402270800b00435da6f3272mr59104356edd.160.1657188106313; Thu, 07 Jul 2022 03:01:46 -0700 (PDT) X-Google-Smtp-Source: AGRyM1sa9itQk8MCQrfGJDkX4tSlr0nI31PyKDn+oNYxgsM/K4ovlzMK3VkwUF9dZvJf9KNmR/8YVg== X-Received: by 2002:a05:6402:2708:b0:435:da6f:3272 with SMTP id y8-20020a056402270800b00435da6f3272mr59104311edd.160.1657188106004; Thu, 07 Jul 2022 03:01:46 -0700 (PDT) Received: from fedora (nat-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id o13-20020a170906768d00b0072af6d20a9asm2372836ejm.75.2022.07.07.03.01.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Jul 2022 03:01:45 -0700 (PDT) From: Vitaly Kuznetsov To: kvm@vger.kernel.org, Paolo Bonzini , Sean Christopherson Cc: Anirudh Rayabharam , Wanpeng Li , Jim Mattson , Maxim Levitsky , linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 08/28] KVM: VMX: Support TSC scaling with enlightened VMCS In-Reply-To: <20220629150625.238286-9-vkuznets@redhat.com> References: <20220629150625.238286-1-vkuznets@redhat.com> <20220629150625.238286-9-vkuznets@redhat.com> Date: Thu, 07 Jul 2022 12:01:44 +0200 Message-ID: <87let5qm0n.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Vitaly Kuznetsov writes: ... > > While on it, update the comment why VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL/ > VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL are kept filtered out ... > + * While GUEST_IA32_PERF_GLOBAL_CTRL and HOST_IA32_PERF_GLOBAL_CTRL > + * are present in eVMCSv1, Windows 11 still has issues booting when > + * VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL/VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL > + * are exposed to it, keep them filtered out. Finally, I got a piece of information from Microsoft on what's going on and it solves a lot of our problems. They did introduce a new PV feature bit indicating support for these new fields in eVMCSv1 and Win11 checks for its presence. This means that we do not need to play the 'eVMCS revisions' trick as CPUID information from VMM is enough. -- Vitaly