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 8DD52C636CD for ; Fri, 10 Feb 2023 16:45:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232681AbjBJQpB (ORCPT ); Fri, 10 Feb 2023 11:45:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56814 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232631AbjBJQo7 (ORCPT ); Fri, 10 Feb 2023 11:44:59 -0500 Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A287F2387B for ; Fri, 10 Feb 2023 08:44:58 -0800 (PST) Received: by mail-pj1-x102c.google.com with SMTP id y11so2037784pjc.0 for ; Fri, 10 Feb 2023 08:44:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=NJHZLI3U8xm4BvE76qEZmYthnYLuvPmE/9R6s6JH2WE=; b=PGoM0On23xN1z29b+slMgbz1TJZwnHKNRVJbC7LasGyUh0C3QyF0n0O8XXt+cqNbLc hJ3dGJWA4ApfbIMG8xBX7DW8YIUESz9H2waScJMhWCHXciylEmamqDndyd0hSbz6hTdU kMm+VcXDMiaQTm+JMifWtE5MXsPj5Ri27EdJ62borjbB/5riiRhUb4EHUx3nd08uv0c5 GS9S9lEin1mSvQot9SnmuiXPZRyKXxwSE/Xj19CEvgqn7JU0MTQsmjNldmMy7QvC9pnD dNMa4zBYDMdlNaobbmicUzL/3IY2ZE+oOCpQGMg4adbatyHii9R9L7J5XyvREuLaIizs vmhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=NJHZLI3U8xm4BvE76qEZmYthnYLuvPmE/9R6s6JH2WE=; b=Gv0HXhQmbFwKKe2Wjf0154cSSVRZKBRfU6rQVQK2NND5vidPC8VaEY4HTYbDHcjqJR G5sedkr4QPuPNWeuiEvoZN2Q0cge85QEKhwvsdO6rVgz/P9D7ZZyauklK7+7Wy94TH/7 mJQ6cbwVAcy3VM7qPGquJOIfZidGDNIX72r8+diOaRUkCYD3ZUPwQy5B4gbL7dSwMo76 695ya1/dloNAVnSaX0GRJnbkXL2H3i9mLy7Xt9+P0zI7cweZfnjdOKsVnc2UbhdT11XS NXwTikFDgM22tNU7CG+6TeZe2IhxWT7V940/79uNL7jwQNkBbB9GGI1hhx4NI47jPKAB jIjg== X-Gm-Message-State: AO0yUKV8bABVe/Tn5aouJGmGuKmwl4VYqHc8OXiFYw8SFOYyyAgNT9yI uP2xQPbNZNrAKoFhstBQ0k3YLw== X-Google-Smtp-Source: AK7set8EuUMVEwEQRgYZK/t2nvIEb1AnNNve/LFQPz8u9HOOPOjZgVuNG4+d/sNDJYJaKvLnXUtKGw== X-Received: by 2002:a17:902:e551:b0:19a:6cd2:a658 with SMTP id n17-20020a170902e55100b0019a6cd2a658mr200687plf.7.1676047497966; Fri, 10 Feb 2023 08:44:57 -0800 (PST) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id i21-20020aa78d95000000b0058119caa82csm3489689pfr.205.2023.02.10.08.44.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Feb 2023 08:44:57 -0800 (PST) Date: Fri, 10 Feb 2023 16:44:53 +0000 From: Sean Christopherson To: Santosh Shukla Cc: Maxim Levitsky , kvm@vger.kernel.org, Sandipan Das , Paolo Bonzini , Jim Mattson , Peter Zijlstra , Dave Hansen , Borislav Petkov , Pawan Gupta , Thomas Gleixner , Ingo Molnar , Josh Poimboeuf , Daniel Sneddon , Jiaxi Chen , Babu Moger , linux-kernel@vger.kernel.org, Jing Liu , Wyes Karny , x86@kernel.org, "H. Peter Anvin" Subject: Re: [PATCH v2 10/11] KVM: SVM: implement support for vNMI Message-ID: References: <20221129193717.513824-1-mlevitsk@redhat.com> <20221129193717.513824-11-mlevitsk@redhat.com> <439a8cfc-fe2d-436d-2ea2-b795eb983b9a@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <439a8cfc-fe2d-436d-2ea2-b795eb983b9a@amd.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 10, 2023, Santosh Shukla wrote: > On 2/1/2023 5:52 AM, Sean Christopherson wrote: > So you mean.. In vNMI mode, KVM should never need to request NMI window and eventually > it reaches to NMI window then WARN_ON and cont.. to single step... so modified code change > may look something like below: > > static void svm_enable_nmi_window(struct kvm_vcpu *vcpu) > { > struct vcpu_svm *svm = to_svm(vcpu); > > /* > * With vNMI we should never need an NMI window. > * and if we reach here then better WARN and continue to single step. > */ > WARN_ON_ONCE(is_vnmi_enabled(svm)); > > if (svm_get_nmi_mask(vcpu) && !svm->awaiting_iret_completion) > return; /* IRET will cause a vm exit */ > > if (!gif_set(svm)) { > if (vgif) > svm_set_intercept(svm, INTERCEPT_STGI); > return; /* STGI will cause a vm exit */ > } > > /* > * Something prevents NMI from been injected. Single step over possible > * problem (IRET or exception injection or interrupt shadow) > */ > > svm->nmi_singlestep_guest_rflags = svm_get_rflags(vcpu); > svm->vmcb->save.rflags |= (X86_EFLAGS_TF | X86_EFLAGS_RF); > svm->nmi_singlestep = true; > } > > Does that make sense? Yep. Though please avoid "we" and other pronouns in changelogs and comments, and wrap as close to the boundary as possible.