Received: by 2002:a05:6358:bb9e:b0:b9:5105:a5b4 with SMTP id df30csp436167rwb; Fri, 2 Sep 2022 17:25:04 -0700 (PDT) X-Google-Smtp-Source: AA6agR6baP/UV3QOyl7qbwpYmS1t5LSLPs8UZpp+j+Dh7AV+wxsdOxtKJmeFjp1/pDGVkyOOw++0 X-Received: by 2002:a17:907:7604:b0:741:4e7a:a1ca with SMTP id jx4-20020a170907760400b007414e7aa1camr21723490ejc.250.1662164703935; Fri, 02 Sep 2022 17:25:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662164703; cv=none; d=google.com; s=arc-20160816; b=IeFlGAtLs2oVonxi6CpI9wLRD8BvOMaCbzJTi4SwvAKINtjk2Baqoykr50vPgsjArV PI5ZzIv3ldYEZmoWKxIhBq+NnvlrXCDvFjZXfJ1fL8PUVxE901qHI1fgXr2AL8BVA/tq 50pEuFpr25OLHMatIuaVyJNIHr0rf8Mfy/tomsdlRgJWZ7eNI42lAO2aGK/d9KOV+g4d weerIw8wBB4oRcs/uh66E9w8f/uAjc9l1OSSQKuT0PtsSWgvPozZxbM3aoiSZlwwfc64 j+bqBn8xwwvz6+YiRFYSKga6IDwnkx03MkCqw0jWpbvQL57KdR/OV3MHwbVKGid3Fvh/ YboQ== 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=H/HByp3PJRruswmtBIPALL6gkH9l79nKV7vcOC9XVxY=; b=eisHlT5ved9KlEWyVuyyXaN2cU6dhpIaOYmR9D+76QQFwQ1TCsyOa1c8WRAvUV+QyT zR7FUft/QLNMRr6jWoKabNY1QwUIVwy804l/hJZSeplTsTLXkjah/Gylpiy6x2jcgHNR ig+T0BsuBX2Owez0xMQM5VVCjdLnbQvZEqKWnC9fhGAAJ64Fy7fGAece5joaDjtfW1mQ qoL61U+UpNOLK9TstxfFrcqdUmhfZ/PZlMPcXOrPyYA7TmJK676yxK9ZDOJIC1+s/CGu 5GZiXydq9oAnWYolBfdsxbqd+DjkDw6+vkf/zPeM5/lALrvsRZrNuDv69ssDJWtAsQjN CvvA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=XOeXnIfK; 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 cb17-20020a0564020b7100b0043b52adbf6esi2405790edb.557.2022.09.02.17.24.36; Fri, 02 Sep 2022 17:25:03 -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=XOeXnIfK; 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 S231251AbiICAXF (ORCPT + 99 others); Fri, 2 Sep 2022 20:23:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53522 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231210AbiICAXC (ORCPT ); Fri, 2 Sep 2022 20:23:02 -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 54EF5F63D7 for ; Fri, 2 Sep 2022 17:23:01 -0700 (PDT) Received: by mail-pl1-x649.google.com with SMTP id l16-20020a170902f69000b00175138bcd25so2117527plg.2 for ; Fri, 02 Sep 2022 17:23:01 -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=H/HByp3PJRruswmtBIPALL6gkH9l79nKV7vcOC9XVxY=; b=XOeXnIfKKWrhWxYJPMhiMqXpVXJ3ObDoI8TdggVIQBpsN4K7qSeFXajmY9O2iBTx1w L8lWlNa1T4AhcE1QV5rKSkfbco2RA0SYCndpTR1CCAteGce251GlAlOPWA2fPHK5ogyR okE4b7f9Eo6DSsCJn5+UyZj3wed8oBAZDnoKGRPKNb/bETmW0pGFie/2OwPvhtME++nG qO61P75YrK5vzJBnTWfQoEcpCJoh2NksjeHN7m9yY3gzIuAbB05/9jv8+Uz79cOZucZj qzW8frIU5J/ReHS6by3eUjEGUQNxkSco1HrwZH33OE8hAtce9untgMSPH6eUq4TXhYTR BxGA== 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=H/HByp3PJRruswmtBIPALL6gkH9l79nKV7vcOC9XVxY=; b=xqQjkaqOpPUxg2qfHcgBBzAqXEXXek+lbr3vf0PSJ6x79KcRzf7DLKuNaKKknRSHpL LLTbxGwm6ykB53pHBeDwOrHLfpd+0LBlNWm25fi/5BFq+p4l6cWL5MO9QyStL88+p+2B /hyiGVuoOi74rOWZ2FNFgIQo+tAYH1cnsEhxZnvG4NPsL8HSowOrZy5tefredNyV22w0 rH2FC4g22Lod/weXLX73B9rTAgc1AAuXeGYn/xdcPuL4a6LV6YWLjOGM0DttX+cEZISW yPVVT0M1y0Zc08swtsQ+us9U05X8yeRJfeTrGUJsykGE8DtD+IKGlMyyuL5IsaWkeICJ XSaw== X-Gm-Message-State: ACgBeo2JEIQex64h9RC6haDZgvcQC9XPESjJ810Nkv5JDAAWhd4pKfCw IOQuKQThSGFU8lz403ioGLF5epmCy7g= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:903:2003:b0:175:24eb:62b0 with SMTP id s3-20020a170903200300b0017524eb62b0mr19360164pla.60.1662164580907; Fri, 02 Sep 2022 17:23:00 -0700 (PDT) Reply-To: Sean Christopherson Date: Sat, 3 Sep 2022 00:22:32 +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-2-seanjc@google.com> Subject: [PATCH v2 01/23] 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, 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=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 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 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 9dda989a1cf0..38e9b8e5278c 100644 --- a/arch/x86/kvm/lapic.c +++ b/arch/x86/kvm/lapic.c @@ -2429,6 +2429,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); @@ -2485,7 +2486,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); @@ -2772,7 +2772,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.2.789.g6183377224-goog