From: Maxim Levitsky <mlevitsk@redhat.com>
To: kvm@vger.kernel.org
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
"H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
Jim Mattson <jmattson@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Joerg Roedel <joro@8bytes.org>,
x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)),
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: [PATCH v4 0/2] KVM: nSVM: ondemand nested state allocation
Date: Thu, 17 Sep 2020 13:10:46 +0300 [thread overview]
Message-ID: <20200917101048.739691-1-mlevitsk@redhat.com> (raw)
This is new version of ondemand nested state allocation.
In this version I dropped the changes to set_efer and instead
added a new request KVM_REQ_OUT_OF_MEMORY which makes the kvm
exit to userspace with KVM_EXIT_INTERNAL_ERROR
This request is used in (unlikely) case of memory allocation
failure.
Maxim Levitsky (2):
KVM: add request KVM_REQ_OUT_OF_MEMORY
KVM: nSVM: implement ondemand allocation of the nested state
arch/x86/kvm/svm/nested.c | 42 ++++++++++++++++++++++++++++++
arch/x86/kvm/svm/svm.c | 54 ++++++++++++++++++++++-----------------
arch/x86/kvm/svm/svm.h | 7 +++++
arch/x86/kvm/x86.c | 7 +++++
include/linux/kvm_host.h | 1 +
5 files changed, 87 insertions(+), 24 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-17 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 10:10 Maxim Levitsky [this message]
2020-09-17 10:10 ` [PATCH v4 1/2] KVM: add request KVM_REQ_OUT_OF_MEMORY Maxim Levitsky
2020-09-17 10:10 ` [PATCH v4 2/2] KVM: nSVM: implement ondemand allocation of the nested state Maxim Levitsky
2020-09-17 16:29 ` Sean Christopherson
2020-09-19 15:09 ` Paolo Bonzini
2020-09-20 16:16 ` Sean Christopherson
2020-09-20 16:42 ` Paolo Bonzini
2020-09-21 7:53 ` Maxim Levitsky
2020-09-21 8:57 ` Maxim Levitsky
2020-09-21 13:23 ` Maxim Levitsky
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=20200917101048.739691-1-mlevitsk@redhat.com \
--to=mlevitsk@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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