From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 85F57C001DF for ; Sat, 29 Jul 2023 01:42:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232402AbjG2BmZ (ORCPT ); Fri, 28 Jul 2023 21:42:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53240 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234323AbjG2BmG (ORCPT ); Fri, 28 Jul 2023 21:42:06 -0400 Received: from mail-pg1-x54a.google.com (mail-pg1-x54a.google.com [IPv6:2607:f8b0:4864:20::54a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BF09549EC for ; Fri, 28 Jul 2023 18:41:17 -0700 (PDT) Received: by mail-pg1-x54a.google.com with SMTP id 41be03b00d2f7-55c79a5564cso1777452a12.3 for ; Fri, 28 Jul 2023 18:41:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1690594875; x=1691199675; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=etHIErEcW2Snp48GMQTn4g9bxzrUdUzMcla8D7qkAKU=; b=NYiDMaTVhIAWqq2Ku68RdD957FUpBniR7RICpd5Ta09Re7OeUgl3W+OEMsjWPdln08 CJUpUT+gN+e7y12/Jmtw9OK/yUGfFrF0aCGTfISkVXFlrfzCfe6JEhpxpQxcSfXu4Zar QFlbWgnGGbV2L7tbZ3Ml+7OSARYS6BW1hrXOYGgW8AR729AU438PBsH8dUTu0xLfuOVM /cZ/Guv0sEuG/xN+qbxm8Fmks6OZNOYfX087Ejj0cZXQc84D35YWo4l9+6yMV7vnh9WY GTn0ni7vkbyhH3Fjlt9O2wGe37ppCa/NiCE1vyOifDl+V3vRrHTZmlxHlaajqNl/WpeH cGvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690594875; x=1691199675; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=etHIErEcW2Snp48GMQTn4g9bxzrUdUzMcla8D7qkAKU=; b=EeXDmA3KVLPaioREvmTecAEgbdQrTKGSb1fJ8OaEQtCw1izPW+iwrg9D2LRLk45Z0q hAPfn69h2AwvHfpgH+p/HPQqmxW6rVP9vd7qGtolIan9hteTp9s7CwLrIINA+X12RZ4A N7PsoSqlbHchE12CFoPHgOQG+q8EhmxCwPSDVzdsiscKc7xXumnP2vslGeJDjmSTpIkp aNoJd27hlxy6K3ug874ZL5ygVsHghY56AgiYyL4hEIR3WbfG7SQLttylDFzyRkBl0DNY 9Ex79T1eOb7Q2Xswn6WehePwaL4DZP0lOT1J4cpkHGj8iPkNW8D3cf29kl8fYpzZIt36 u59g== X-Gm-Message-State: ABy/qLblWYE21SnzlXfMe6TIlZ5B9MsZSiqK7VxB2HQhQVp3BnxjEKf8 RTSvHA4L6EwpDWHQRx3eBc+oM+FBgxk= X-Google-Smtp-Source: APBJJlEgel2xyk023tQstWnd108PwEKYO8pRsbSFOhwxNCzG4vrLLyhebl7F/zmViiPb+nRZMMcJ8NjGMt4= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:903:2445:b0:1bb:c7bc:ce9a with SMTP id l5-20020a170903244500b001bbc7bcce9amr13831pls.10.1690594873732; Fri, 28 Jul 2023 18:41:13 -0700 (PDT) Date: Fri, 28 Jul 2023 18:41:12 -0700 In-Reply-To: <20230726135945.260841-1-mlevitsk@redhat.com> Mime-Version: 1.0 References: <20230726135945.260841-1-mlevitsk@redhat.com> Message-ID: Subject: Re: [PATCH v2 0/3] Fix 'Spurious APIC interrupt (vector 0xFF) on CPU#n' issue From: Sean Christopherson To: Maxim Levitsky Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, Borislav Petkov , Paolo Bonzini , Dave Hansen , Thomas Gleixner , "H. Peter Anvin" , Ingo Molnar Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 26, 2023, Maxim Levitsky wrote: > Maxim Levitsky (3): > KVM: x86: VMX: __kvm_apic_update_irr must update the IRR atomically > KVM: x86: VMX: set irr_pending in kvm_apic_update_irr > KVM: x86: check the kvm_cpu_get_interrupt result before using it > > arch/x86/kvm/lapic.c | 25 +++++++++++++++++-------- > arch/x86/kvm/x86.c | 10 +++++++--- > 2 files changed, 24 insertions(+), 11 deletions(-) Paolo, are you still planning on taking these directly? I can also grab them and send them your way next week. I have a couple of (not super urgent, but kinda urgent) fixes for 6.5 that I'm planning on sending a PULL request for, just didn't get around to that today.