Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp1654013rwl; Thu, 5 Jan 2023 17:32:57 -0800 (PST) X-Google-Smtp-Source: AMrXdXtl6eY3enCigumP8chkJbwpRaOpeyuyKuMj4yN27qcpg1zNbV37L9C8OrWAFBnmYsTAcwl8 X-Received: by 2002:a17:902:6a85:b0:191:420e:e6b1 with SMTP id n5-20020a1709026a8500b00191420ee6b1mr54461976plk.32.1672968777124; Thu, 05 Jan 2023 17:32:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672968777; cv=none; d=google.com; s=arc-20160816; b=QLj8AUBBMmAFKEfn5lVemnO/FvlzE2O/Ck0H70eFOkhBCMefdx0m+BP0ZxzwfJ4iHZ bhQsrlKd8+N4LkjGTr1uwHY+uIxoPNI+yEEgLWXhCMh1opRp7a6QONS3f3KTbXqcCTGX wHrYwqTDVpPeuULpCaHmq2i+MxdUgqaee8AC1kAizj0HL9WOTKZEi7y9Zj+dee6TVx9Q vi5DC2CugCDXo8aLh5DHupN+B8xT0R48LNUQDb2qraqLRXSsHRcbHKEThl0rtAlrWIrS WURsOx75l7fGzOzZUiX5UWCqM9+iRBdygkPAvZEo5onnhSPA3ifmlGYxgSq7b64tl/Oj AEvQ== 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=U8maFLX/9emtR9Ry3/JNGkiRA36hfakt5AevFKMRuP8=; b=HvmCqV/A+iCO9xaArhjgG2jvWPWXpV206DexhrG1R1X82yZq1QqhyefEb+txP4lzD5 rBPf+sAP7JsceNolAhWwn0Li1Bs/0qh6bs8OBI/aufSha5+1sNaTYMqqcG45OcxQcWTk QwfnkAl9qg+32BAiiApk3PT2sfqJky8OuEeQ3E7lTLFIBKp2SVCXMbmsgM1JG0nRHRvC euq474SwfMVtrMaGMKGBpuDH/AHdU2xnxpmXysmGm73Yqnfb2RgDSNqBqYj1I9xOX5VB P6EeKf8/p/jio7ov+eETgMFmleQZFeLSQ6vKISn7+hfUBh6YdmpHS8QpMSBx2RtQasFH KMOQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=FDPrant3; 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 j9-20020a170902da8900b00189655d51f5si9581321plx.260.2023.01.05.17.32.50; Thu, 05 Jan 2023 17:32:57 -0800 (PST) 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=FDPrant3; 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 S236822AbjAFBNp (ORCPT + 55 others); Thu, 5 Jan 2023 20:13:45 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37230 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236749AbjAFBNT (ORCPT ); Thu, 5 Jan 2023 20:13:19 -0500 Received: from mail-yb1-xb49.google.com (mail-yb1-xb49.google.com [IPv6:2607:f8b0:4864:20::b49]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7197771FFF for ; Thu, 5 Jan 2023 17:13:18 -0800 (PST) Received: by mail-yb1-xb49.google.com with SMTP id e12-20020a25500c000000b007b48c520262so404740ybb.14 for ; Thu, 05 Jan 2023 17:13:18 -0800 (PST) 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:message-id:reply-to; bh=U8maFLX/9emtR9Ry3/JNGkiRA36hfakt5AevFKMRuP8=; b=FDPrant3hMVGIRHqyuyr8ArImAU9GINekaycon8t2xlOdFMNVNZY2cfGp0nNw3dW54 1YV8Mw5cRxet3a+fCY7wJLIyCFO+s+iduPSgPyfflvb4tI3HdFebsvVT/RF4xz+4pSLV y7TOm5efaEc8M6aB8SfVAptefpHTx7ufHNShtJqwyMyfJpJahK5EL2U96+WqZ8FMIgVA kq1odA7Dq6Tu960vucowHuolVI4IKR8t0nCJ5A42s5tnCxEgJYQOG66ZPcBVtw3fOblC DAR7OoG1RW2vUBQAGf7wezgsWKDd2kS64Z/vT8wohB9aNZGcNQqnf2tO3CsF/v7HnCxc BPEw== 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:message-id :reply-to; bh=U8maFLX/9emtR9Ry3/JNGkiRA36hfakt5AevFKMRuP8=; b=yd+RzVMa1EGEijy9r+xt5lKc/ISzB8ztoWkOt5WXzp7piRvrRnRssdlrwlRLeLIoqL msmqbxrssCTVNpFVlatjY2vqJwdvjr7sqZPYYuYK0+mnCSK9B66nWBvqQOoS/jvdtIEB dHgu1i0CA0fiRdwhad2VazilXlo0jbo1N+TT+r70MrhfAxzWVRH95Q1vqzIQFne1PiCL 2bEJKF/HdYRTw7Tefa/cRHN0RwQLiOsIxMIQE7EZJgzCWrFBCXBQIY83j+hXlBrx9hOT nmRpTxw+JOkC8XmSQ+2oFnhh9t0VVJWw6ChxSf+SvoFKmf9BY+Nwis4z5fqXvLQ9DvII g9vA== X-Gm-Message-State: AFqh2kqClANCOTa1HgPrxeRnaTnUJk0ic8YNYekCWCUHTUeiMoCThwEz YFG+XGcGremlKW32x4T8850C/3dMPRs= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a25:a087:0:b0:700:a7b4:1af9 with SMTP id y7-20020a25a087000000b00700a7b41af9mr3497734ybh.227.1672967597770; Thu, 05 Jan 2023 17:13:17 -0800 (PST) Reply-To: Sean Christopherson Date: Fri, 6 Jan 2023 01:12:35 +0000 In-Reply-To: <20230106011306.85230-1-seanjc@google.com> Mime-Version: 1.0 References: <20230106011306.85230-1-seanjc@google.com> X-Mailer: git-send-email 2.39.0.314.g84b9a713c41-goog Message-ID: <20230106011306.85230-3-seanjc@google.com> Subject: [PATCH v5 02/33] 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 , Maxim Levitsky , Suravee Suthikulpanit , Li RongQing , Greg Edwards 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 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 Reviewed-by: 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 5c0f93fc073a..33a661d82da7 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; } void kvm_lapic_reset(struct kvm_vcpu *vcpu, bool init_event) @@ -2479,7 +2480,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.39.0.314.g84b9a713c41-goog