From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Cathy Avery <cavery@redhat.com>,
Liran Alon <liran.alon@oracle.com>,
Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH 0/7] KVM: SVM: baby steps towards nested state migration
Date: Mon, 18 May 2020 13:07:27 -0700 [thread overview]
Message-ID: <27c7526c-4d02-c9ba-7d3b-7416dbe4cdbb@oracle.com> (raw)
In-Reply-To: <20200515174144.1727-1-pbonzini@redhat.com>
On 5/15/20 10:41 AM, Paolo Bonzini wrote:
> Here are some refactorings to prepare for an SVM implementation of
> KVM_SET_NESTED_STATE. It's a prerequisite for that to eliminate
> exit_required, moving exceptions to svm_check_nested_events. However:
>
> - I might work on that soon, because it's needed to handle RSM when
> the L1 hypervisor wants to get it from #UD rather than the specific
> RSM intercept
>
> - this should be enough to get a quick prototype, that I need in order to
> debug a particularly crazy bug and figure out its reproducibility.
>
> So, I am getting these patches out of my todo list for now.
>
> Thanks,
>
> Paolo
>
> Paolo Bonzini (7):
> KVM: SVM: move map argument out of enter_svm_guest_mode
> KVM: SVM: extract load_nested_vmcb_control
> KVM: SVM: extract preparation of VMCB for nested run
> KVM: SVM: save all control fields in svm->nested
> KVM: nSVM: remove HF_VINTR_MASK
> KVM: nSVM: do not reload pause filter fields from VMCB
> KVM: SVM: introduce data structures for nested virt state
>
> arch/x86/include/asm/kvm_host.h | 1 -
> arch/x86/include/uapi/asm/kvm.h | 26 +++++++-
> arch/x86/kvm/svm/nested.c | 115 +++++++++++++++++---------------
> arch/x86/kvm/svm/svm.c | 11 ++-
> arch/x86/kvm/svm/svm.h | 28 +++++---
> 5 files changed, 116 insertions(+), 65 deletions(-)
>
Reviewed-by: Krish Sadhukhan <krish.sadhukhan@oracle.com>
next prev parent reply other threads:[~2020-05-18 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 17:41 [PATCH 0/7] KVM: SVM: baby steps towards nested state migration Paolo Bonzini
2020-05-15 17:41 ` [PATCH 1/7] KVM: SVM: move map argument out of enter_svm_guest_mode Paolo Bonzini
2020-05-15 17:41 ` [PATCH 2/7] KVM: SVM: extract load_nested_vmcb_control Paolo Bonzini
2020-05-15 23:09 ` Krish Sadhukhan
2020-05-15 23:34 ` Paolo Bonzini
2020-05-15 17:41 ` [PATCH 3/7] KVM: SVM: extract preparation of VMCB for nested run Paolo Bonzini
2020-05-15 23:36 ` Paolo Bonzini
2020-05-15 17:41 ` [PATCH 4/7] KVM: SVM: save all control fields in svm->nested Paolo Bonzini
2020-05-15 17:41 ` [PATCH 5/7] KVM: nSVM: remove HF_VINTR_MASK Paolo Bonzini
2020-05-15 17:41 ` [PATCH 6/7] KVM: nSVM: do not reload pause filter fields from VMCB Paolo Bonzini
2020-05-15 17:41 ` [PATCH 7/7] KVM: SVM: introduce data structures for nested virt state Paolo Bonzini
2020-05-18 20:07 ` Krish Sadhukhan [this message]
2020-05-18 20:11 ` [PATCH 0/7] KVM: SVM: baby steps towards nested state migration Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27c7526c-4d02-c9ba-7d3b-7416dbe4cdbb@oracle.com \
--to=krish.sadhukhan@oracle.com \
--cc=cavery@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).