[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210504143936.1644378-1-mlevitsk@redhat.com>
Date: Tue, 4 May 2021 17:39:34 +0300
From: Maxim Levitsky <mlevitsk@...hat.com>
To: kvm@...r.kernel.org
Cc: Borislav Petkov <bp@...en8.de>,
Paolo Bonzini <pbonzini@...hat.com>,
x86@...nel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)),
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, Cathy Avery <cavery@...hat.com>,
Sean Christopherson <seanjc@...gle.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Joerg Roedel <joro@...tes.org>,
Maxim Levitsky <mlevitsk@...hat.com>
Subject: [PATCH v2 0/2] KVM: nSVM: few fixes for the nested migration
Those are few fixes for issues I uncovered by doing variants of a
synthetic migration test I just created:
I modified the qemu, such that on each vm pause/resume cycle,
just prior to resuming a vCPU, qemu reads its KVM state,
then (optionaly) resets this state by uploading a
dummy reset state to KVM, and then it uploads back to KVM,
the state that this vCPU had before.
V2: those are only last 2 patches from V1,
updated with review feedback from Paolo (Thanks!).
Best regards,
Maxim Levitsky
Maxim Levitsky (2):
KVM: nSVM: always restore the L1's GIF on migration
KVM: nSVM: remove a warning about vmcb01 VM exit reason
arch/x86/kvm/svm/nested.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.26.2
Powered by blists - more mailing lists