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:     Sean Christopherson <seanjc@google.com>, x86@kernel.org,
        Kees Cook <keescook@chromium.org>,
        Dave Hansen <dave.hansen@linux.intel.com>,
        linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
        Borislav Petkov <bp@alien8.de>, Joerg Roedel <joro@8bytes.org>,
        Ingo Molnar <mingo@redhat.com>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Vitaly Kuznetsov <vkuznets@redhat.com>,
        Wanpeng Li <wanpengli@tencent.com>,
        Jim Mattson <jmattson@google.com>,
        Maxim Levitsky <mlevitsk@redhat.com>
Subject: [PATCH v2 00/11] SMM emulation and interrupt shadow fixes
Date:   Tue, 21 Jun 2022 18:08:51 +0300
Message-Id: <20220621150902.46126-1-mlevitsk@redhat.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

This patch series is a result of long debug work to find out why=0D
sometimes guests with win11 secure boot=0D
were failing during boot.=0D
=0D
During writing a unit test I found another bug, turns out=0D
that on rsm emulation, if the rsm instruction was done in real=0D
or 32 bit mode, KVM would truncate the restored RIP to 32 bit.=0D
=0D
I also refactored the way we write SMRAM so it is easier=0D
now to understand what is going on.=0D
=0D
The main bug in this series which I fixed is that we=0D
allowed #SMI to happen during the STI interrupt shadow,=0D
and we did nothing to both reset it on #SMI handler=0D
entry and restore it on RSM.=0D
=0D
Best regards,=0D
	Maxim Levitsky=0D
=0D
Maxim Levitsky (11):=0D
  KVM: x86: emulator: em_sysexit should update ctxt->mode=0D
  KVM: x86: emulator: introduce update_emulation_mode=0D
  KVM: x86: emulator: remove assign_eip_near/far=0D
  KVM: x86: emulator: update the emulation mode after rsm=0D
  KVM: x86: emulator: update the emulation mode after CR0 write=0D
  KVM: x86: emulator/smm: number of GPRs in the SMRAM image depends on=0D
    the image format=0D
  KVM: x86: emulator/smm: add structs for KVM's smram layout=0D
  KVM: x86: emulator/smm: use smram struct for 32 bit smram load/restore=0D
  KVM: x86: emulator/smm: use smram struct for 64 bit smram load/restore=0D
  KVM: x86: SVM: use smram structs=0D
  KVM: x86: emulator/smm: preserve interrupt shadow in SMRAM=0D
=0D
 arch/x86/include/asm/kvm_host.h |   6 -=0D
 arch/x86/kvm/emulate.c          | 305 ++++++++++++++++----------------=0D
 arch/x86/kvm/kvm_emulate.h      | 146 +++++++++++++++=0D
 arch/x86/kvm/svm/svm.c          |  28 +--=0D
 arch/x86/kvm/x86.c              | 162 ++++++++---------=0D
 5 files changed, 394 insertions(+), 253 deletions(-)=0D
=0D
-- =0D
2.26.3=0D
=0D