From: eric van tassell <Eric.VanTassell@amd.com>
To: kvm@vger.kernel.org
Cc: bp@alien8.de, hpa@zytor.com, mingo@redhat.com,
jmattson@google.com, joro@8bytes.org, pbonzini@redhat.com,
sean.j.christopherson@intel.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org,
evantass@amd.com
Subject: [Patch 0/4] Defer page pinning for SEV guests until guest pages touched
Date: Fri, 24 Jul 2020 18:54:44 -0500 [thread overview]
Message-ID: <20200724235448.106142-1-Eric.VanTassell@amd.com> (raw)
Overview
========
Defer pinning of the guest's pages until nested page faults occur
to improve startup time and reduce memory pressure for SEV guests.
Cease paying the computational cost of pinning all pages when an
encrypted region is registered, before it is known if they will be accessed.
Cease creating the memory pressure due to pinning all pages when an
encrypted region is registered before, it is known if they will be accessed.
Timing Results
==========
All timings are done by hand with and Android stopwatch app
SEV guest size(GiB) | 4 | 8 | 16 | 32 | 60 |
without patch series(sec) | 2 | 3 | 4 | 8 | 14 |
with patch series (sec) | 1 | 1 | 1 | 1 | 1 |
Applies To:
===========
This patch applies top of this commit from the <next> branch of
the kvm tree:
c34b26b98cac Tianjia Zhang : KVM: MIPS: clean up redundant 'kvm_run' parameters
eric van tassell (4):
KVM:MMU: Introduce the set_spte_notify() callback
KVM:SVM: Introduce set_spte_notify support
KVM:SVM: Pin sev_launch_update_data() pages via sev_get_page()
KVM:SVM: Remove struct enc_region and associated pinned page tracking.
arch/x86/include/asm/kvm_host.h | 3 +
arch/x86/kvm/mmu/mmu.c | 31 ++++-
arch/x86/kvm/mmu/paging_tmpl.h | 27 ++--
arch/x86/kvm/svm/sev.c | 232 ++++++++++++++++----------------
arch/x86/kvm/svm/svm.c | 2 +
arch/x86/kvm/svm/svm.h | 4 +-
6 files changed, 169 insertions(+), 130 deletions(-)
--
2.17.1
next reply other threads:[~2020-07-24 23:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 23:54 eric van tassell [this message]
2020-07-24 23:54 ` [Patch 1/4] KVM:MMU: Introduce the set_spte_notify() callback eric van tassell
2020-07-24 23:54 ` [Patch 2/4] KVM:SVM: Introduce set_spte_notify support eric van tassell
2020-07-31 20:25 ` Sean Christopherson
2020-08-02 20:53 ` Eric van Tassell
2020-08-03 16:27 ` Sean Christopherson
2020-08-19 16:03 ` Eric van Tassell
2020-08-19 16:05 ` Sean Christopherson
2020-08-20 17:05 ` Eric van Tassell
2020-08-20 23:59 ` Sean Christopherson
2020-08-21 0:36 ` Eric van Tassell
2020-08-21 18:16 ` Eric van Tassell
2020-07-24 23:54 ` [Patch 3/4] KVM:SVM: Pin sev_launch_update_data() pages via sev_get_page() eric van tassell
2020-07-31 20:40 ` Sean Christopherson
2020-08-02 23:55 ` Eric van Tassell
2020-08-19 16:20 ` Eric van Tassell
2020-07-24 23:54 ` [Patch 4/4] KVM:SVM: Remove struct enc_region and associated pinned page tracking eric van tassell
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=20200724235448.106142-1-Eric.VanTassell@amd.com \
--to=eric.vantassell@amd.com \
--cc=bp@alien8.de \
--cc=evantass@amd.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).