RE: [RFC v1 0/2] Plumbing to support multiple secure memory backends.
On Wed, Oct 14, 2020 at 07:31:17AM +0100, Christoph Hellwig wrote: > Please don't add an abstraction without a second implementation. > Once we have the implementation we can consider the tradeoffs. E.g. > if expensive indirect function calls are really needed vs simple > branches. Ok. Not planning on upstreaming these patches till we have atleast another backend. -- Ram Pai
Re: [RFC v1 0/2] Plumbing to support multiple secure memory backends.
Please don't add an abstraction without a second implementation. Once we have the implementation we can consider the tradeoffs. E.g. if expensive indirect function calls are really needed vs simple branches.
[RFC v1 0/2] Plumbing to support multiple secure memory backends.
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