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;
From:   Maxim Levitsky <mlevitsk@redhat.com>
To:     kvm@vger.kernel.org
Cc:     Borislav Petkov <bp@alien8.de>,
        Paolo Bonzini <pbonzini@redhat.com>,
        x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)),
        Wanpeng Li <wanpengli@tencent.com>,
        Jim Mattson <jmattson@google.com>,
        "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        linux-kernel@vger.kernel.org, Cathy Avery <cavery@redhat.com>,
        Sean Christopherson <seanjc@google.com>,
        Vitaly Kuznetsov <vkuznets@redhat.com>,
        Joerg Roedel <joro@8bytes.org>,
        Maxim Levitsky <mlevitsk@redhat.com>
Subject: [PATCH v2 0/2] KVM: nSVM: few fixes for the nested migration
Date:   Tue,  4 May 2021 17:39:34 +0300
Message-Id: <20210504143936.1644378-1-mlevitsk@redhat.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Those are few fixes for issues I uncovered by doing variants of a=0D
synthetic migration test I just created:=0D
=0D
I modified the qemu, such that on each vm pause/resume cycle,=0D
just prior to resuming a vCPU, qemu reads its KVM state,=0D
then (optionaly) resets this state by uploading a=0D
dummy reset state to KVM, and then it uploads back to KVM,=0D
the state that this vCPU had before.=0D
=0D
V2: those are only last 2 patches from V1,=0D
updated with review feedback from Paolo (Thanks!).=0D
=0D
Best regards,=0D
	Maxim Levitsky=0D
=0D
Maxim Levitsky (2):=0D
  KVM: nSVM: always restore the L1's GIF on migration=0D
  KVM: nSVM: remove a warning about vmcb01 VM exit reason=0D
=0D
 arch/x86/kvm/svm/nested.c | 3 ++-=0D
 1 file changed, 2 insertions(+), 1 deletion(-)=0D
=0D
-- =0D
2.26.2=0D
=0D