From: Ram Pai <linuxram@us.ibm.com>
To: kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: farosas@linux.ibm.com, linuxram@us.ibm.com, bharata@linux.ibm.com
Subject: [RFC v1 0/2] Plumbing to support multiple secure memory backends.
Date: Mon, 12 Oct 2020 00:27:41 -0700 [thread overview]
Message-ID: <1602487663-7321-1-git-send-email-linuxram@us.ibm.com> (raw)
Secure VMs are currently supported by the Ultravisor backend.
Enhance the plumbing to support multiple backends. Each backend shall
provide the implementation for the necessary and sufficient calls
in order to support secure VM.
Also as part of this change, modify the ultravisor implementation to
be a plugin that provides an implementation of the backend.
Ram Pai (2):
KVM: PPC: Book3S HV: rename all variables in book3s_hv_uvmem.c
KVM: PPC: Book3S HV: abstract secure VM related calls.
arch/powerpc/include/asm/kvm_book3s_uvmem.h | 100 ---------
arch/powerpc/include/asm/kvmppc_svm_backend.h | 250 ++++++++++++++++++++++
arch/powerpc/kvm/book3s_64_mmu_radix.c | 6 +-
arch/powerpc/kvm/book3s_hv.c | 28 +--
arch/powerpc/kvm/book3s_hv_uvmem.c | 288 +++++++++++++++-----------
5 files changed, 432 insertions(+), 240 deletions(-)
delete mode 100644 arch/powerpc/include/asm/kvm_book3s_uvmem.h
create mode 100644 arch/powerpc/include/asm/kvmppc_svm_backend.h
--
1.8.3.1
next reply other threads:[~2020-10-12 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 7:27 Ram Pai [this message]
2020-10-12 7:27 ` [RFC v1 1/2] KVM: PPC: Book3S HV: rename all variables in book3s_hv_uvmem.c Ram Pai
2020-10-12 7:27 ` [RFC v1 2/2] KVM: PPC: Book3S HV: abstract secure VM related calls Ram Pai
2020-10-12 15:28 ` Bharata B Rao
2020-10-12 16:13 ` Ram Pai
2020-10-14 6:31 ` [RFC v1 0/2] Plumbing to support multiple secure memory backends Christoph Hellwig
2020-10-14 19:30 ` Ram Pai
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=1602487663-7321-1-git-send-email-linuxram@us.ibm.com \
--to=linuxram@us.ibm.com \
--cc=bharata@linux.ibm.com \
--cc=farosas@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).