Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp91262rwb; Fri, 30 Sep 2022 18:01:50 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5I0ULuj2EuH/Wkam4zuh6es0gqsS6H55bxIRiYHlUkSSAAGM3x+1Vng8EoJku2PyaMm3V4 X-Received: by 2002:a63:cf48:0:b0:439:7d1c:fedc with SMTP id b8-20020a63cf48000000b004397d1cfedcmr9859607pgj.281.1664586110268; Fri, 30 Sep 2022 18:01:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664586110; cv=none; d=google.com; s=arc-20160816; b=b5C0iL3zD4PWOl+FqcTvr66T2IqMBsjhyWvqqTQSkseZ75MBu4LYfdxeo9nJNvp6RD VQVdP6yU7l0wiNVjf1SELRF5yhnB/NaOaOm7zrJ+GanPer7SQjNC28Es8KVxmkoKQgae 1L4//FgUnLUdT3495+S6aTivdxfsLgf6X8TWTi+sM2eJ8PYgjzSsxPgSRStKujSIN/Na fal+MidpIBouf9nFmeyf0IOXsjbaD4l2A/TyaP/L85jPneYxWv3E/BYKn7eXAMF3p6dB HLBpYEDXgn/Wlsmc7O7sNCqNXFjqJskjSyyH8PAaAT9EvSkiBabjCGLEwaQ/hO+/gydZ DSkQ== 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=9HZnxxV4Lu47qHeGw+m4H8xJT/iB8E+mQuPsqkTLvZo=; b=nYk1QjGq3yCU8y+YtPTN3WU+H49Ogkv+wThwhde9ADdOErLxGiV9accNS1EZKLIuX5 6uYIx8Alu10gLY+8EQy2HpLLDf25PHu9dVniw+g74fjLpXybqobbU3VWM18cF0KmYcOv xv3SgauLDCEjktQqlT0W2FR3t/NROEmR5sn6eW1ZQJZwdJ/UH5e7fTcO93LOGAjSOMSC airXNJDLp4WbnzFXrGuq6I/dyVKZGWlGdoeL9I6Xa3T1Z1sPCwb9DufQR3DsgKVY+ohy TyXdqlctsVnPqX8+mahJLMShwkZ/hd23zsU+WXeTEotxqpnWu369m11UH/DTutCTjtTr 4x+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=EgHb1LRJ; 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 k12-20020aa788cc000000b0054ed3047ee2si1721176pff.22.2022.09.30.18.01.25; Fri, 30 Sep 2022 18:01:50 -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=EgHb1LRJ; 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 S232786AbiJAA7b (ORCPT + 99 others); Fri, 30 Sep 2022 20:59:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36914 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231298AbiJAA7X (ORCPT ); Fri, 30 Sep 2022 20:59:23 -0400 Received: from mail-yb1-xb4a.google.com (mail-yb1-xb4a.google.com [IPv6:2607:f8b0:4864:20::b4a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 47C691AF90C for ; Fri, 30 Sep 2022 17:59:22 -0700 (PDT) Received: by mail-yb1-xb4a.google.com with SMTP id y65-20020a25c844000000b006bb773548d5so5153743ybf.5 for ; Fri, 30 Sep 2022 17:59:22 -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=9HZnxxV4Lu47qHeGw+m4H8xJT/iB8E+mQuPsqkTLvZo=; b=EgHb1LRJAwUhJDvw+Tu8ye1lUjtrA6UHF9kIPSVNUM46EliRJePeMD8MaXA/YtgT5P RHpNWWsXhSZcnyX/BpAJkXdiqIBiUBj5Z9l4PQ2H8GUfHlM1YGTqG4Dm3cCZkcCwM2CH ELe5C0tQtConxuuviisk/6Xq+NMUMnDlZhVvEm7USg2qbd3XI5LJnAnWoN31foRIL1gd 75uYfoPofiVnFwLTi36WSQPAid3GAkreU3c7wXDabIFyUzG7sEQN84lgZyme+akaDcLH pPu350uwcQ09MuIUAIuzS7+V1QUnMQDq82h+Y3zELbFso/K8oFiLliQB/9XBoWDcaKUj 0bOA== 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=9HZnxxV4Lu47qHeGw+m4H8xJT/iB8E+mQuPsqkTLvZo=; b=CfsjarnsO+2yUdXjI7YfRw6Mp8TRiGgNt42+9JCAGkPdaxIGEqoQr2cxhxJGlaFWT4 uekXJ7D30k6vg66KfEIzXtvKh7qlrYpvUu9zGmp7NRPvncHMRK6h7rodpy//cI0aTz1V eKHOUfOzwm+jyqVfGYwgHgUYWQv/AmyBgnDLtEvYKPhLBkcTwRYGqFIq6atrCCymtSj2 Q5ZEJZg7wmoFALbX2kCvcVlMzYx/lPCd2EZjx971i32vic4Hw2DlV1sZgXBeC731yu1K cHxVgkCfCkv3km274wFuSo+ZC6Wt8xcs5tvhOf+Z5Tw76BLpYwFoMgWCcQTiwQ4e2hU8 khag== X-Gm-Message-State: ACrzQf1nMXVaKHBkj8q4bR3pl0oTAj6HOJFDYEXm5PMsnuWbE/7jHVeN sRRXjZztnbrco86lJQhFK8MC44gSG7I= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a25:a007:0:b0:6a9:3b58:31f with SMTP id x7-20020a25a007000000b006a93b58031fmr10317698ybh.44.1664585961604; Fri, 30 Sep 2022 17:59:21 -0700 (PDT) Reply-To: Sean Christopherson Date: Sat, 1 Oct 2022 00:58:45 +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-3-seanjc@google.com> Subject: [PATCH v4 02/32] 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 05d079fc2c66..5de1c7aa1ce9 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.38.0.rc1.362.ged0d419d3c-goog