Received: by 2002:a05:6358:bb9e:b0:b9:5105:a5b4 with SMTP id df30csp436237rwb; Fri, 2 Sep 2022 17:25:08 -0700 (PDT) X-Google-Smtp-Source: AA6agR5WoDZ8/EdJ0xFR19IbHH8A13y94v2kaLbZnMcabC53uJh6Uo/bm0yFzME/vifQONj2qeXQ X-Received: by 2002:a17:907:7fac:b0:741:4247:d856 with SMTP id qk44-20020a1709077fac00b007414247d856mr22178868ejc.565.1662164708717; Fri, 02 Sep 2022 17:25:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662164708; cv=none; d=google.com; s=arc-20160816; b=a0JC8oUqGY9cqhgUjUB7rkA3rSLXMZ0yBWf3bFKGx6UOOKs3eH+FJGliRQNOZ++G3E WsY+L/wTZGCZTFGSxCpUur+NIIWUyd7dqnhXBShtMqREbChIHR3YIFVmeT68qDCliVx4 hx00yNLa2eqglYj6OGtjQ9atLTI2y1vTtfIKWrOmzHbkwbiMOFHbFpZKkrIEruRVRXav esynED1cJqfQDbZ4Bl6m4YWR5NMgYpoJ/JrBMqGBasON4I51wwzPhsSUDa/txOmt8LEI 7TmJ7KYfHKm3cm/O5dfIvvGKN8clt+Mi+zsxTiBH6ObgXyjQr6lNCz3Z8IZuX1G0c3Hl Sifw== 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=PIDwOUCtBewPHDMb4tVnQLyazdcuUyhDknKis4oP5e8=; b=T0Ddk+QMyIOWmyjBTPINJdgqfcaZqQxniytKaCVYpFd1Uidlx/RlGSezDyd/r/ed1P uQCHCvGrHxEMQpu3wgDCXFYBdf0NK6a2OSzpTSk3MYr9WkIBQGeQbEZmTyNxK2Njjr1J 1qGG5qGjvTpvGrN80qtz70bvY6BvNcpV49Iox5khsM22rJp2inLJ7bpew8HDMjsxWwlD QI+Why1sxiR+IL+T/jYZD9prggCubEaozpN6ODXbAmaERnthmzMgiKDfy7PPiT6E9EXa pgrLQapjt1y3bm3FSADDmgjYnH+lZYBo5AQj2LsvdG83fx42UDppUNO0Rprz8WtWBMM/ TVQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=b26qyh04; 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 l27-20020a50d6db000000b004481b74d9f7si2305065edj.577.2022.09.02.17.24.43; Fri, 02 Sep 2022 17:25:08 -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=b26qyh04; 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 S231298AbiICAXJ (ORCPT + 99 others); Fri, 2 Sep 2022 20:23:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53532 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231229AbiICAXD (ORCPT ); Fri, 2 Sep 2022 20:23:03 -0400 Received: from mail-pl1-x649.google.com (mail-pl1-x649.google.com [IPv6:2607:f8b0:4864:20::649]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1F69DF63D1 for ; Fri, 2 Sep 2022 17:23:03 -0700 (PDT) Received: by mail-pl1-x649.google.com with SMTP id q8-20020a170902dac800b001753aa66955so2101670plx.5 for ; Fri, 02 Sep 2022 17:23:03 -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=PIDwOUCtBewPHDMb4tVnQLyazdcuUyhDknKis4oP5e8=; b=b26qyh04/+cVHoGaCuXAqwfdfxKioKFeVh+lEW/sxDvmCTO3oJmQMLOMgwljALZBsD FkreDci/td/b1kRcO0MrT91dOY0G2C7HdUrjl3OuGNSQNupfaqWxDJ1yqXRCs7ZSrQMK 0pJc/1N94lJJtFkXyrDq5C5+VgB/hFB3pyO2vh6Ke/KEijK7zzdp/upEqeBhKF56MwKE NZoLhOnkS1Uk2aT34zv2+SYjCHz4SPgYrJfFkrmrRT/SX9Lnp5aAt0vN7/pAukCI/sMW GvtL2RswZWw+4y3y55nOthTlNDXetxJviFpHoNwQkcO5cLiocnE6UYkq08ei5lETSpTa UzEQ== 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=PIDwOUCtBewPHDMb4tVnQLyazdcuUyhDknKis4oP5e8=; b=eJjY4Zb0JihFSls899Cn+FApVLLivw9v0qtvpDF3wpkLKEw8RQ1DBD8/73p2MJCgok Zt6EGRKVxTidmqtNM/5F9LNdqXKzkKO6bAvMR4M5s3kivvaWIrdwC1EjjCdsfgBg+Xos C9yrEGIioIo1R+s+lXWh+gj3Y7HNrY/U4fKu4TbbI5AvIPb+5r1gBt3PNXrUpwQoCIfv Si1+Ln4l169kGSUKLZ/PhadsUoFa/udYq32d8NYkVxAWvSWViu/TX+vuQun+rCzg9Ml3 wiH669Q/T+vGTaO6/quM4ReNLFWz17ITTSMEv4L7FqGyfI1Yw9ZAgvhZ4YGENRR+wM8X X9iA== X-Gm-Message-State: ACgBeo1eVO8pA8k9MtGs0L60Sxuh3lhcqwQqVXVse6NtoKrpvzIQHt59 P5IUqibOnnkH9YSFD+gqZFPDtpwjMPw= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a62:b519:0:b0:537:9723:5cf2 with SMTP id y25-20020a62b519000000b0053797235cf2mr39060596pfe.15.1662164582631; Fri, 02 Sep 2022 17:23:02 -0700 (PDT) Reply-To: Sean Christopherson Date: Sat, 3 Sep 2022 00:22:33 +0000 In-Reply-To: <20220903002254.2411750-1-seanjc@google.com> Mime-Version: 1.0 References: <20220903002254.2411750-1-seanjc@google.com> X-Mailer: git-send-email 2.37.2.789.g6183377224-goog Message-ID: <20220903002254.2411750-3-seanjc@google.com> Subject: [PATCH v2 02/23] 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, 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,T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL autolearn=ham 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(). 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..4fbef2af1efc 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 + * mappings 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.37.2.789.g6183377224-goog