Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp4045686pxy; Tue, 4 May 2021 16:38:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkGKRR8Ksn2CaUp8ZE2q4CcKNmOdLeaLKy2T9Tsrg+ywqfDEfAr6rKuekaX3GbVRv/M/ly X-Received: by 2002:aa7:cf19:: with SMTP id a25mr29210069edy.231.1620171517752; Tue, 04 May 2021 16:38:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620171517; cv=none; d=google.com; s=arc-20160816; b=0q3WZZe3cq/CT4jjCFNI3EtzCEPKkWAZmXAtx2TWEPM3bmO7cQ2paswose4bcs/0oA YNqL8srb3xtXA7iOfFi7ADsJTEZ9PEuqD1FxVv1ahT/6BOgPgAnfvWFuLwEj4DqOOrp3 BOMm8ypq1lnnSMh2+mVc6+s9XsiGYDT06OIlf2OuaB7jDEypqzzL+8+aSBzQROqEH4eC 6eHF6/61IAqTseLdBNsJHbghFblSKBbgHVKOfiTLrMyZqIjrZpEBKTu+N3VkJQqespbN L4Lwdvu7odLwBB2xMIrgmr8h706lbW1pKxPgD5aVRoAJNSD142xDJKjgH8Ep//yRuDIP 7/Ug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=VqtYvGK2HW/675ICBPcjqx1NTuB+M4OsXaqpSs46khM=; b=SYkz2jDkY2nK4EN3URBWxFOlOdIMqVZQRwspYhPRCL5k+njZs39pGfU+FKW66lHIOA dfOUga707llf+H4r9yMXFLM/8M232Y0S47aXJsieheGX+BhMdbK9QKbkaJpM2KASMQUL dlfqCACSRXexuZhh2Bpv4ra0LQ/E8vnmE9bMJwstJOPDsBGdYOgd4I5n4wx97wlTzhzE 5I7mED/NPakvsApqm9/gAB0n0LH20UxaBOj/FFI6KGHciVbUHQm1jlOuo9rLgaukpIwF IPtvAgIbAFAoV/kdI8ZuSsxQCRkWS5rbt1l5TwR8njQ+WrwqsgbVdQKm1EI8vsoSwIPY cQXQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b="QVzEY1/U"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i15si4724758ejz.1.2021.05.04.16.38.14; Tue, 04 May 2021 16:38:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b="QVzEY1/U"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S232410AbhEDVwD (ORCPT + 99 others); Tue, 4 May 2021 17:52:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44292 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231478AbhEDVwC (ORCPT ); Tue, 4 May 2021 17:52:02 -0400 Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B8B14C061574 for ; Tue, 4 May 2021 14:51:07 -0700 (PDT) Received: by mail-pf1-x42e.google.com with SMTP id i190so336320pfc.12 for ; Tue, 04 May 2021 14:51:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=VqtYvGK2HW/675ICBPcjqx1NTuB+M4OsXaqpSs46khM=; b=QVzEY1/U66ql90TgUkNXnanon4r1J+F8V1Gt1Z4s5/5TrMs+tD6bjJBjsnHFJrxGVR Tv0S9Sn1fBbNgOUIjsxdlfVTxK/6zGH1tetbrj8jx4/EYzbPzKav2DSWMBklIxj7KQfW /bZVW6cSqc7tV9B6ciuT5EKNmyDR4V6gzpao7w+D83KB+Kt0E8YJh8GIcK/Vc8S21uQV 95ameDL+aEyLlr7sXj7zFJtXQ1arJ1nZSBUPjyj7w0gz+a3/kDtG4RKe+s0rBjhJwm00 OhcvNYRi39aziHoPnkjAIEhP9sM3PDO9P17WlJeKHhtw2ELJNPoql9V1fPXdsgfcZNCY 4NYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=VqtYvGK2HW/675ICBPcjqx1NTuB+M4OsXaqpSs46khM=; b=PpVKFomkIFiVnLQgj21y8c1iBIgV7qmCNOzdbDEuW82m/FAHRxs6EqjcfbEfXOjjPz FF7ChcbDiYQHm7QnjUY72RAguGhJ7AezEZZXlv1ue5DGnqK2s+KlQ2WZTt66LYxWfwAD IAfFvlC4SytXkj7BzhJtXHxM0Ii9Sai9C8+wasQuc/myFLpK4jitAG6JHzy09IaKI7HO tc9Ph1rfs9XWGjn8F7+TWuJlFeuF+v3V9vEexyUdLOSMVPi4lZ6fSEXkxgbBxf4X6jTA f4Pxs99eix0zqmuXBEPORHzcOsrCKigitq7DPHmFr7yrohESzd9AdwcXS/QbLzWb35LJ NxEA== X-Gm-Message-State: AOAM532tYNJ8ptuXpO5dP2UBZLwMCP6CfZlJMLdtyCtKOjq1936DK4+l irhUjhEtfEkiw/4owtePJldSPg== X-Received: by 2002:a17:90a:280d:: with SMTP id e13mr7873857pjd.191.1620165067168; Tue, 04 May 2021 14:51:07 -0700 (PDT) Received: from google.com (240.111.247.35.bc.googleusercontent.com. [35.247.111.240]) by smtp.gmail.com with ESMTPSA id l64sm4655029pgd.20.2021.05.04.14.51.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 May 2021 14:51:06 -0700 (PDT) Date: Tue, 4 May 2021 21:51:02 +0000 From: Sean Christopherson To: Paolo Bonzini Cc: Andy Lutomirski , Maxim Levitsky , Thomas Gleixner , Lai Jiangshan , linux-kernel@vger.kernel.org, Lai Jiangshan , Steven Rostedt , Andi Kleen , Andy Lutomirski , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Josh Poimboeuf , Uros Bizjak , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H. Peter Anvin" , Peter Zijlstra , Alexandre Chartre , Juergen Gross , Joerg Roedel , Jian Cai Subject: Re: [PATCH] KVM/VMX: Invoke NMI non-IST entry instead of IST entry Message-ID: References: <38B9D60F-F24F-4910-B2DF-2A57F1060452@amacapital.net> <625057c7-ea40-4f37-8bea-cddecfe1b855@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <625057c7-ea40-4f37-8bea-cddecfe1b855@redhat.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 04, 2021, Paolo Bonzini wrote: > On 04/05/21 23:23, Andy Lutomirski wrote: > > > On May 4, 2021, at 2:21 PM, Sean Christopherson wrote: > > > FWIW, NMIs are masked if the VM-Exit was due to an NMI. > > Huh, indeed: "An NMI causes subsequent NMIs to be blocked, but only after > the VM exit completes". > > > Then this whole change is busted, since nothing will unmask NMIs. Revert it? SMI? #MC? :-) > Looks like the easiest way out indeed. I've no objection to reverting to intn, but what does reverting versus handling NMI on the kernel stack have to do with NMIs being blocked on VM-Exit due to NMI? I'm struggling mightily to connect the dots.