Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp4010936iog; Tue, 28 Jun 2022 07:19:12 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vZP8EnyAwirX5eUTDtloe/AF/8+8jmyDQJ64jt0md3g3UyXckDp51U3uQw8H7HqK9sJIFJ X-Received: by 2002:a17:902:7582:b0:16a:307a:5965 with SMTP id j2-20020a170902758200b0016a307a5965mr5158087pll.159.1656425952502; Tue, 28 Jun 2022 07:19:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656425952; cv=none; d=google.com; s=arc-20160816; b=kFq3u8UyRcXd8wyh/AYjuIkcU1T/0GtkCcpI+MWhbf4CeT8KKu36DnndfmvgKvLydX ygMwPmSioM/i1+RdG8nguhN90bg2GbwKpQvp/QEcn4RLCWgJynoMmMjbDwBHjaKOtreF qO0hNhZVXEB1deSn/M5L3ToQlsKT1T60lt4tXYSQ4hjxvSkXB4ehNJjpF5bAyMGEJGe9 B1F8S1ZGKgN6MiEfGsugWb7Mb/f7fY4p6PAxgi5QPRkZP86koQZJ8OutTVIJiJcWLKQS 6BwWFo61TLE7EcsKMpNWnIybMvrnxs+HXWM1sEIQlyPM02iGejuEBDto7qENfeGe3jGG Y6NA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=tCQ95kskG0LV6RyOc6915lftS4TkDvmZ/mGLATm2CXA=; b=hK8/kBzk72zcAYqDysPOKvpgU5lJg1OSNxadOiTcc5mHirv74T7c/I6ViiCOYvKIyN Z1KV83M3OvsHaQP1r+FWTi39QAobVgsK1KJ9/fyAQ8AW2lrYTLYp1GizoOkWo1+AMgLQ uNW3wdpWPZLw0z5iNyVkH0vzgSxTymags7PciKC6bLxV4R4Nad/HiFqxgBtA5ymnGBgS U0TuiYnXIFmJOEB8oOrV83M16qQyvmqwJaDxEXZeskvMg4Y+pAJyy9/rb8VFPY4bUtiE P3PScNtN6qqnsw66BWLAi8eW9zQasZB45jryAGp2grzuxYm4ejFA0qosBOOFV2Z+HQaV /u/A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gFuVt3aK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j70-20020a638049000000b0040d40aa9825si16146590pgd.867.2022.06.28.07.18.55; Tue, 28 Jun 2022 07:19:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gFuVt3aK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347385AbiF1OEO (ORCPT + 99 others); Tue, 28 Jun 2022 10:04:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44194 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347381AbiF1OEJ (ORCPT ); Tue, 28 Jun 2022 10:04:09 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 3D7F72F38A for ; Tue, 28 Jun 2022 07:04:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1656425047; 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=tCQ95kskG0LV6RyOc6915lftS4TkDvmZ/mGLATm2CXA=; b=gFuVt3aK7zPoTw/HvBSpvFvIMcyAO7rqmLZIrMKbJandbOPZEoN+WYGKVlPP2Axvj8lhnc O6FcjbfPVQyBWqe5BsSFeWCsptZ4JkbcU3xhSBw1qyZrpCAGfl9RdTW0qCVMoF1oHZAkwZ XEOGvgKiut8kNwBLLYInFnHyfmRbPXg= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-610-XknUWZpeO7up2g9OWCkntg-1; Tue, 28 Jun 2022 10:04:05 -0400 X-MC-Unique: XknUWZpeO7up2g9OWCkntg-1 Received: by mail-wr1-f70.google.com with SMTP id l9-20020adfa389000000b0021b8b489336so1828332wrb.13 for ; Tue, 28 Jun 2022 07:04:05 -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=tCQ95kskG0LV6RyOc6915lftS4TkDvmZ/mGLATm2CXA=; b=HnklX15OnqBq/189r55gcw/K34xBv0A+BcHgl+843Pb/NJCPFn26n2LDKUBgIL7rv2 dMPE/PIBEc9h6rWKSN8fgytyPYWtl+/mviIWWSaD5T04R5WmbjrT3VUMljyWeROxMs2W /mwmQr+Vw3IguAuZ5KOU+WNjruuvduYySmwHIOKOt6C8xsTce8v5B/ocr4vs/3WLvrYD jOXu+FLeAaNxRZi4ZAf8STsJWnMgsCv8RLKcMmF/SlhRQ43DOSHVl1fMIDRky7l8B9I+ RwhC5QE/68XDxCsu48Wu83RtiCLNPEPtAfxPLc54TAG5fx9BpSk2pKGgJzqXCuhZyMc8 LdVg== X-Gm-Message-State: AJIora+5oVxNSGmshMcf3Oe7wrt40TFmPvR/2d8CEjusybgJAXQb0dCh m2p8eEHtBFO/E6b/kUI3JyA0wgpmzZIqJ+6/rgDWAOR4JFNIho0mYvak/sKNHEE+lwDQ6owtpcN W9mqhSIyVxxAZrUdsRFzJiKirlAG3BIQEbc+2alFqK91TZu2KxCKQzEK9nyqtEC56cvEN12WlmO td X-Received: by 2002:a5d:5a02:0:b0:21b:939d:65c5 with SMTP id bq2-20020a5d5a02000000b0021b939d65c5mr17751630wrb.417.1656425044366; Tue, 28 Jun 2022 07:04:04 -0700 (PDT) X-Received: by 2002:a5d:5a02:0:b0:21b:939d:65c5 with SMTP id bq2-20020a5d5a02000000b0021b939d65c5mr17751596wrb.417.1656425044079; Tue, 28 Jun 2022 07:04:04 -0700 (PDT) Received: from fedora (nat-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id w9-20020a5d6089000000b0020e5b4ebaecsm13855180wrt.4.2022.06.28.07.04.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Jun 2022 07:04:03 -0700 (PDT) From: Vitaly Kuznetsov To: Jim Mattson Cc: kvm@vger.kernel.org, Paolo Bonzini , Sean Christopherson , Anirudh Rayabharam , Wanpeng Li , Maxim Levitsky , linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/14] KVM: nVMX: Use vmcs_config for setting up nested VMX MSRs In-Reply-To: References: <20220627160440.31857-1-vkuznets@redhat.com> Date: Tue, 28 Jun 2022 16:04:02 +0200 Message-ID: <87y1xgubot.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jim Mattson writes: > On Mon, Jun 27, 2022 at 9:04 AM Vitaly Kuznetsov wrote: >> >> Changes since RFC: >> - "KVM: VMX: Extend VMX controls macro shenanigans" PATCH added and the >> infrastructure is later used in other patches [Sean] PATCHes 1-3 added >> to support the change. >> - "KVM: VMX: Clear controls obsoleted by EPT at runtime, not setup" PATCH >> added [Sean]. >> - Commit messages added. >> >> vmcs_config is a sanitized version of host VMX MSRs where some controls are >> filtered out (e.g. when Enlightened VMCS is enabled, some know bugs are >> discovered, some inconsistencies in controls are detected,...) but >> nested_vmx_setup_ctls_msrs() uses raw host MSRs instead. This may end up >> in exposing undesired controls to L1. Switch to using vmcs_config instead. >> >> Sean Christopherson (1): >> KVM: VMX: Clear controls obsoleted by EPT at runtime, not setup >> >> Vitaly Kuznetsov (13): >> KVM: VMX: Check VM_ENTRY_IA32E_MODE in setup_vmcs_config() >> KVM: VMX: Check CPU_BASED_{INTR,NMI}_WINDOW_EXITING in >> setup_vmcs_config() >> KVM: VMX: Tweak the special handling of SECONDARY_EXEC_ENCLS_EXITING >> in setup_vmcs_config() >> KVM: VMX: Extend VMX controls macro shenanigans >> KVM: VMX: Move CPU_BASED_CR8_{LOAD,STORE}_EXITING filtering out of >> setup_vmcs_config() >> KVM: VMX: Add missing VMEXIT controls to vmcs_config >> KVM: VMX: Add missing VMENTRY controls to vmcs_config >> KVM: VMX: Add missing CPU based VM execution controls to vmcs_config >> KVM: nVMX: Use sanitized allowed-1 bits for VMX control MSRs >> KVM: VMX: Store required-1 VMX controls in vmcs_config >> KVM: nVMX: Use sanitized required-1 bits for VMX control MSRs >> KVM: VMX: Cache MSR_IA32_VMX_MISC in vmcs_config >> KVM: nVMX: Use cached host MSR_IA32_VMX_MISC value for setting up >> nested MSR >> >> arch/x86/kvm/vmx/capabilities.h | 16 +-- >> arch/x86/kvm/vmx/nested.c | 37 +++--- >> arch/x86/kvm/vmx/nested.h | 2 +- >> arch/x86/kvm/vmx/vmx.c | 198 ++++++++++++++------------------ >> arch/x86/kvm/vmx/vmx.h | 118 +++++++++++++++++++ >> 5 files changed, 229 insertions(+), 142 deletions(-) >> >> -- >> 2.35.3 >> > > Just checking that this doesn't introduce any backwards-compatibility > issues. That is, all features that were reported as being available in > the past should still be available moving forward. > All the controls nested_vmx_setup_ctls_msrs() set are in the newly introduced KVM_REQ_VMX_*/KVM_OPT_VMX_* sets so we should be good here (unless I screwed up, of course). There's going to be some changes though. E.g this series was started by Anirudh's report when KVM was exposing SECONDARY_EXEC_TSC_SCALING while running on KVM and using eVMCS which doesn't support the control. This is a bug and I don't think we need and 'bug compatibility' here. Another change is that VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL/ VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL will now be filtered out on the "broken" CPUs (the list is in setup_vmcs_config()). I *think* this is also OK but if not, we can move the filtering to vmx_vmentry_ctrl()/ vmx_vmexit_ctrl(). -- Vitaly