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;
From:   Maxim Levitsky <mlevitsk@redhat.com>
To:     kvm@vger.kernel.org
Cc:     Paolo Bonzini <pbonzini@redhat.com>,
        Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Dave Hansen <dave.hansen@linux.intel.com>,
        linux-kernel@vger.kernel.org,
        Peter Zijlstra <peterz@infradead.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Sandipan Das <sandipan.das@amd.com>,
        Daniel Sneddon <daniel.sneddon@linux.intel.com>,
        Jing Liu <jing2.liu@intel.com>,
        Josh Poimboeuf <jpoimboe@kernel.org>,
        Wyes Karny <wyes.karny@amd.com>,
        Borislav Petkov <bp@alien8.de>,
        Babu Moger <babu.moger@amd.com>,
        Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
        Sean Christopherson <seanjc@google.com>,
        Jim Mattson <jmattson@google.com>, x86@kernel.org,
        Maxim Levitsky <mlevitsk@redhat.com>
Subject: [PATCH 00/13] SVM: vNMI (with my fixes)
Date:   Thu, 17 Nov 2022 16:32:29 +0200
Message-Id: <20221117143242.102721-1-mlevitsk@redhat.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi!=0D
=0D
This is the vNMI patch series from Santosh Shukla with few=0D
small fixes from me:=0D
=0D
1. When a vNMI injection is pending, then to allow to not=0D
  delay for an unbounded time the injection of another NMI that could=0D
  arrive before the first vNMI injection is done, I added the code=0D
  that would intercept IRET/RSM/STGI and then try the injection again.=0D
=0D
2. I slighlty modified the 'KVM: SVM: Add VNMI support in get/set_nmi_mask'=
=0D
   to have WARN_ON in vNMI functions when called without vNMI enabled.=0D
   Also NMI mask/unmask should be allowed regardless if SMM is active,=0D
   to support migration.=0D
=0D
3. I did some refactoring in the code which updates the int_ctl in vmcb12=0D
   on nested VM exit, and updated the patch 'KVM: nSVM: implement nested VN=
MI'=0D
   to use this.=0D
=0D
4. I added my reviewed-by to all the patches which I didn't change.=0D
=0D
I only tested this on a machine which doesn't have vNMI, so this does need=
=0D
some testing to ensure that nothing is broken.=0D
=0D
Another thing I haven't looked at in depth yet is migration, I think there =
is a bug=0D
because with vNMI, now in practise we can have 2 NMIs injected to the guest=
,=0D
one in service, one 'pending injection' but no longer pending from KVM poin=
t of view,=0D
and the KVM doesn't take this in account in kvm_vcpu_ioctl_x86_get_vcpu_eve=
nts,a=0D
and maybe more.=0D
=0D
Best regards,=0D
       Maxim Levitsky=0D
=0D
Maxim Levitsky (5):=0D
  KVM: nSVM: don't sync back tlb_ctl on nested VM exit=0D
  KVM: nSVM: don't call nested_sync_control_from_vmcb02 on each VM exit=0D
  KVM: nSVM: rename nested_sync_control_from_vmcb02 to=0D
    nested_sync_int_ctl_from_vmcb02=0D
  KVM: nSVM: clean up copying of int_ctl fields back to vmcb01/vmcb12=0D
  KVM: SVM: allow NMI window with vNMI=0D
=0D
Santosh Shukla (8):=0D
  x86/cpu: Add CPUID feature bit for VNMI=0D
  KVM: SVM: Add VNMI bit definition=0D
  KVM: SVM: Add VNMI support in get/set_nmi_mask=0D
  KVM: SVM: Report NMI not allowed when Guest busy handling VNMI=0D
  KVM: SVM: Add VNMI support in inject_nmi=0D
  KVM: nSVM: implement nested VNMI=0D
  KVM: nSVM: emulate VMEXIT_INVALID case for nested VNMI=0D
  KVM: SVM: Enable VNMI feature=0D
=0D
 arch/x86/include/asm/cpufeatures.h |  1 +=0D
 arch/x86/include/asm/svm.h         |  7 +++=0D
 arch/x86/kvm/svm/nested.c          | 84 +++++++++++++++++++++---------=0D
 arch/x86/kvm/svm/svm.c             | 60 ++++++++++++++++++---=0D
 arch/x86/kvm/svm/svm.h             | 70 ++++++++++++++++++++++++-=0D
 5 files changed, 189 insertions(+), 33 deletions(-)=0D
=0D
-- =0D
2.34.3=0D
=0D