Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp102561rwb; Fri, 30 Sep 2022 18:15:17 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4Jf+EoJrcrmOrpA2rNwoDPhe0SoCCDZIN9i607hVkLMdvw4Q8DlpBh0lmkomJf3hjcpuem X-Received: by 2002:a17:907:70c:b0:740:33f3:cbab with SMTP id xb12-20020a170907070c00b0074033f3cbabmr8270926ejb.600.1664586917523; Fri, 30 Sep 2022 18:15:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664586917; cv=none; d=google.com; s=arc-20160816; b=UmV2zNBnUKKW8ndYoWvUAmAaUfXfS0jLIb6YpcijC2BbdJ69cEBt0iPlQlqXCXMV68 lUQU78QX9Ei9uYuTEruEmFW+uVFHFMptO8ohm0ueQcxap1ar65MhYK206SvVcYLxSmuw v70NtH0rLDO/BQDqpEHxpTo27jD86ymyCyiqHFrqUTP0fIxE9Et7pCAqtN97Yh39/tcN 7FO1oNP8bgmdOYtK3ZskrgfaBc4/L/A2r7u7G9UgUprk9kLgea6Uc9+Ryh+d90aoyZeE jM6TsHP39pyZK6KBZqJ3VDNgSPNA4WHGHQ+P7S4aIXNQ8EIDbvaWdtTIKtfY6N+mq8o3 C/Mg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:reply-to:dkim-signature; bh=gWKbedEYDM+WgMEZuaaXsHPdTjjpS3BqpA6Whi9EiUA=; b=sonQ1K6vwYLH8OvUAw8+wnQR0X23iCkd0G/ly4lDX6kHY3cJWmY+TI3AZBySCoAiTg cOLJHm3Ki3pfTuFX4LwWl7XGbn1IAhvnwNF86zTvcNqUfn2SNSeCOm8d+pAOmTPVk0Bj imjW5zM8Stz6cWgq+HXh0su2GSuCR5UtRgNZqOCd213L1JqpoFduHlXW4RnPDah+Agwb o97hR5gFmAiLtUX50EsrIEA+NpoH+sKvqoCTctG7BpjFJGf+NNCbBArwmkasXfy5wtCt DmWD/4ef+YMtCeNCD9qA82S0e5vLForHMegFergbtuNlwBOgMvI3XDn7YwQ9ZywrSupS EYoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b="LMWP/Zwm"; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bs9-20020a170906d1c900b007836ec6999dsi2418623ejb.904.2022.09.30.18.14.51; Fri, 30 Sep 2022 18:15:17 -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=@google.com header.s=20210112 header.b="LMWP/Zwm"; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232678AbiJAA7k (ORCPT + 99 others); Fri, 30 Sep 2022 20:59:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36968 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231955AbiJAA7Z (ORCPT ); Fri, 30 Sep 2022 20:59:25 -0400 Received: from mail-pg1-x549.google.com (mail-pg1-x549.google.com [IPv6:2607:f8b0:4864:20::549]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5DD8F1AF917 for ; Fri, 30 Sep 2022 17:59:24 -0700 (PDT) Received: by mail-pg1-x549.google.com with SMTP id l72-20020a63914b000000b00434ac6f8214so3703225pge.13 for ; Fri, 30 Sep 2022 17:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:reply-to:from:to:cc:subject:date; bh=gWKbedEYDM+WgMEZuaaXsHPdTjjpS3BqpA6Whi9EiUA=; b=LMWP/ZwmM6mNI84QoaByA7gGMv3UqTyhq7gvWgXvV+gu83W3Xsz5MlcgWVWntOG568 HVYiHsHO9gEuCsJKIR5ZyPrrQFSvnTXvQVWXdsv7W4WHcyq/5DC24dd9IwPWGA6cUdOs shCRfpNnUoRmuPXs91O85K1ECe76YYMC12wNJQT9f91GNEs8BXLas4v2U3oXZmvGKGyJ +sceDgf8U3o8mx28L80DvSeekIQvSi0Egtsjp046zQi9qjLw/QZrMi9yEX1Sy6yR4bXf 5k59U6996zsNYfcRXjFjA7HKVe9O/gOGGxTKQHlogX1uxTUm/Xsp+prVIQ1o063ZqQmv vgoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:reply-to:x-gm-message-state:from:to:cc:subject:date; bh=gWKbedEYDM+WgMEZuaaXsHPdTjjpS3BqpA6Whi9EiUA=; b=P0QQJYFvr7KhC+Krw7AyFudeF6MAIFEyHumYkSETqH65FbrjtA6ZHC+1rDtGhZ7QFa aFRLOcL5K94cayHOyuJ+XTf857eXy9xY4Ygkm49U12Jt8u2no/xsgNF1W+RsmevNMnZj Dzgs2SJ9YF7+eaoOO9IZJ8lihLXCVeudyc2X94SKZHNzHLrM5Tgkn4Xo8FXmYZbpFov9 1/+6MnDZunTZ8ShJn9959g8qd7aq4IgQJmJJPhIbVGgIqqpxBj3Bwu9mBak6pzNnFBRD ztg3pFcfjPY+u1P5W64qeQb/+QGjx6OcHxtc5vP53HnaiyvCtSr6G1WskrV9agauEIZ8 KZ0w== X-Gm-Message-State: ACrzQf3FoFzccaIs0/yUBTzFksBfvxiLfk8SP1xbKiuXPQcYLu/FnW0u HP/e9zNrQqRwaUYXJ/voKk+O9ICDVio= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:90a:c986:b0:205:f08c:a82b with SMTP id w6-20020a17090ac98600b00205f08ca82bmr517109pjt.1.1664585963402; Fri, 30 Sep 2022 17:59:23 -0700 (PDT) Reply-To: Sean Christopherson Date: Sat, 1 Oct 2022 00:58:46 +0000 In-Reply-To: <20221001005915.2041642-1-seanjc@google.com> Mime-Version: 1.0 References: <20221001005915.2041642-1-seanjc@google.com> X-Mailer: git-send-email 2.38.0.rc1.362.ged0d419d3c-goog Message-ID: <20221001005915.2041642-4-seanjc@google.com> Subject: [PATCH v4 03/32] KVM: SVM: Flush the "current" TLB when activating AVIC From: Sean Christopherson To: Sean Christopherson , Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Alejandro Jimenez , Suravee Suthikulpanit , Maxim Levitsky , Li RongQing Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-9.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL 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 Flush the TLB when activating AVIC as the CPU can insert into the TLB while AVIC is "locally" disabled. KVM doesn't treat "APIC hardware disabled" as VM-wide AVIC inhibition, and so when a vCPU has its APIC hardware disabled, AVIC is not guaranteed to be inhibited. As a result, KVM may create a valid NPT mapping for the APIC base, which the CPU can cache as a non-AVIC translation. Note, Intel handles this in vmx_set_virtual_apic_mode(). Reviewed-by: Paolo Bonzini Cc: stable@vger.kernel.org Signed-off-by: Sean Christopherson --- arch/x86/kvm/svm/avic.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/arch/x86/kvm/svm/avic.c b/arch/x86/kvm/svm/avic.c index 6919dee69f18..712330b80891 100644 --- a/arch/x86/kvm/svm/avic.c +++ b/arch/x86/kvm/svm/avic.c @@ -86,6 +86,12 @@ static void avic_activate_vmcb(struct vcpu_svm *svm) /* Disabling MSR intercept for x2APIC registers */ svm_set_x2apic_msr_interception(svm, false); } else { + /* + * Flush the TLB, the guest may have inserted a non-APIC + * mapping into the TLB while AVIC was disabled. + */ + kvm_make_request(KVM_REQ_TLB_FLUSH_CURRENT, &svm->vcpu); + /* For xAVIC and hybrid-xAVIC modes */ vmcb->control.avic_physical_id |= AVIC_MAX_PHYSICAL_ID; /* Enabling MSR intercept for x2APIC registers */ -- 2.38.0.rc1.362.ged0d419d3c-goog