Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp4594256rwb; Tue, 20 Sep 2022 16:53:12 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7DtvSyirCDaTDPI2B1l40YkTQVMbjgu5X5PG7kUG9v+ELGmJ7geXcVmhBn6l7TJEkUbS6l X-Received: by 2002:a17:907:6d90:b0:77c:68a8:a5b with SMTP id sb16-20020a1709076d9000b0077c68a80a5bmr19396419ejc.342.1663717992603; Tue, 20 Sep 2022 16:53:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663717992; cv=none; d=google.com; s=arc-20160816; b=EIxGSiWHoNPg+BRgS6ho2ExMoZkJ7TrYFVda0v2wdqFk+7fjIm15h/ktM7HAIeHIqt PPpp9JtqoOXXCmnfqL+0T5+u62/Z+PFADpvxbiQIAHAxfEGNDrtX7cOR5v/DQDUOeJb/ dt/x4VP37eozYr3Zk5guM0accujxWTHBz1kfi4gktmJ7bs1npTSYYmcX3ldf4SbdSSy9 ymuCqEC0lL5JyTAUm9/QE0zCLc6utaPBgalEEGM4E9lMfdINWsjgxG7VnHZI3V/5blGJ G0mlU/7snK0b9HIUqJpnvBqVtufhihlZaPSzd82yrjJ6iS1nPcWTR/48XSpM4XrGT+zm 8qLg== 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=eDQhk0TUzS8gABrZyzO6jP9wbkUSKRsfywOJ1wwDdEA=; b=wqZveihygzIadZHeMaHlsxSXmHTlZsm5tFFJtvCs95lTmthdMFVcIxmMoDpe0MyEBe E5C6mGdGmN33I+F3u8UuRv78gCwjC9En5mVI318JRckwiFcW3raWqtvg3pdhhtib0It0 EPN4RiC7NtsSkxBB5i7g8CW5lFTj0wLxd8+GPdpsEiVfyiQkXHigh1DKRe9JH9J1T/1t 4k3mqDKyrTlb1Cj6wz3cbg/hwqrcj5ZeMk/BkGgsILmKNc4oG637cLmTif0vJRJ1wUv9 hTvPaZVF4vJLGS13poT8vjCxbZTXm6oAzem+KygVQ6LOlAPeP5zAc4RwuD9nqJktdWPi cADg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=MhL2fiHh; 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 e13-20020a170906844d00b0077b2ad71224si951449ejy.136.2022.09.20.16.52.47; Tue, 20 Sep 2022 16:53: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=@google.com header.s=20210112 header.b=MhL2fiHh; 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 S230466AbiITXbu (ORCPT + 99 others); Tue, 20 Sep 2022 19:31:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44642 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229805AbiITXbl (ORCPT ); Tue, 20 Sep 2022 19:31:41 -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 B6AB95E64E for ; Tue, 20 Sep 2022 16:31:40 -0700 (PDT) Received: by mail-pl1-x649.google.com with SMTP id p12-20020a170902e74c00b00177f3be2825so2637175plf.17 for ; Tue, 20 Sep 2022 16:31:40 -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=eDQhk0TUzS8gABrZyzO6jP9wbkUSKRsfywOJ1wwDdEA=; b=MhL2fiHhjRRJdJQeolFFDjGCBCjU5Icnq07HSKUApe1o+vJEuBqSCyOieoYCaP368V 7joOK0RZTSZLGcyaD9pNXyNvuYq/1pzxl59Xb8ACZHav63d3CCIcfY0ADOuMVUJrmIsq 4Tzs058ItmTmfo8vD5p3CgaMvPbgvw1qyJt0/fmggnFMBupeDoR/JX2veJojcsVtj5rP /Od0TDVGTYthl1lOC5/89a3M+2SIAdzVjiHam7KKPjYmzXkueqCBsV9CvmZ6zAqgtnZ6 DRUvUzmWC9m/f+rwMpzDQVMu2v2q4EoROrV2n2ZR166h8NZDxQZgCbV0QJgTiIpZy/sv YXyg== 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=eDQhk0TUzS8gABrZyzO6jP9wbkUSKRsfywOJ1wwDdEA=; b=hs8V4/uRwpIkRPlY32f139BkoX3gi++wbiImnqmC+UHQT8e18xJMkKty1l58MzoEgL koyakd0K4KFibgxvWWNIKEe/bHhjw/t0xsiKkasfQzqmbf870VI/vs8RUtB86XqdZJvH aUi5sCxQXp4YiTSpF8uI66pMK8E7bTKljnA0dBjKl5sBjIUh+HO1NMgZCIuWlYrILMWa LkRC89xP2l8O1Rv6EzZDT6blPqoge9aQG4n2StNui3AquyGLphWFLPunDwpHEhxY9Unl /VU6OTk97/wjtnxC5esIoeL/5eGBNqmUVdrQ11mMmsj5gN4wowqudv2LTkdJnC5c4PpM trsQ== X-Gm-Message-State: ACrzQf0HFBkeNd5fgayN6OB1maYf+IE9rEdkDF2omF3s42lkXeKbNe4j vydOxC0R9TbREgjqZM3AMpzkU/vns0w= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:aa7:90ce:0:b0:547:1cf9:40e6 with SMTP id k14-20020aa790ce000000b005471cf940e6mr26018655pfk.11.1663716700319; Tue, 20 Sep 2022 16:31:40 -0700 (PDT) Reply-To: Sean Christopherson Date: Tue, 20 Sep 2022 23:31:08 +0000 In-Reply-To: <20220920233134.940511-1-seanjc@google.com> Mime-Version: 1.0 References: <20220920233134.940511-1-seanjc@google.com> X-Mailer: git-send-email 2.37.3.968.ga6b4b080e4-goog Message-ID: <20220920233134.940511-3-seanjc@google.com> Subject: [PATCH v3 02/28] KVM: x86: Purge "highest ISR" cache when updating APICv state 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=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 Purge the "highest ISR" cache when updating APICv state on a vCPU. The cache must not be used when APICv is active as hardware may emulate EOIs (and other operations) without exiting to KVM. This fixes a bug where KVM will effectively block IRQs in perpetuity due to the "highest ISR" never getting reset if APICv is activated on a vCPU while an IRQ is in-service. Hardware emulates the EOI and KVM never gets a chance to update its cache. Fixes: b26a695a1d78 ("kvm: lapic: Introduce APICv update helper function") Cc: stable@vger.kernel.org Cc: Suravee Suthikulpanit Cc: Maxim Levitsky Reviewed-by: Paolo Bonzini Signed-off-by: Sean Christopherson --- arch/x86/kvm/lapic.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c index 8004c4d0a8e5..adac6ca9b7dc 100644 --- a/arch/x86/kvm/lapic.c +++ b/arch/x86/kvm/lapic.c @@ -2424,6 +2424,7 @@ void kvm_apic_update_apicv(struct kvm_vcpu *vcpu) */ apic->isr_count = count_vectors(apic->regs + APIC_ISR); } + apic->highest_isr_cache = -1; } EXPORT_SYMBOL_GPL(kvm_apic_update_apicv); @@ -2480,7 +2481,6 @@ void kvm_lapic_reset(struct kvm_vcpu *vcpu, bool init_event) kvm_lapic_set_reg(apic, APIC_TMR + 0x10 * i, 0); } kvm_apic_update_apicv(vcpu); - apic->highest_isr_cache = -1; update_divide_count(apic); atomic_set(&apic->lapic_timer.pending, 0); @@ -2767,7 +2767,6 @@ int kvm_apic_set_state(struct kvm_vcpu *vcpu, struct kvm_lapic_state *s) __start_apic_timer(apic, APIC_TMCCT); kvm_lapic_set_reg(apic, APIC_TMCCT, 0); kvm_apic_update_apicv(vcpu); - apic->highest_isr_cache = -1; if (apic->apicv_active) { static_call_cond(kvm_x86_apicv_post_state_restore)(vcpu); static_call_cond(kvm_x86_hwapic_irr_update)(vcpu, apic_find_highest_irr(apic)); -- 2.37.3.968.ga6b4b080e4-goog