Hi, A pseries guest can be run as a secure guest on Ultravisor-enabled POWER platforms. On such platforms, this driver will be used to manage the movement of guest pages between the normal memory managed by hypervisor(HV) and secure memory managed by Ultravisor(UV). Private ZONE_DEVICE memory equal to the amount of secure memory available in the platform for running secure guests is created. Whenever a page belonging to the guest becomes secure, a page from this private device memory is used to represent and track that secure page on the HV side. The movement of pages between normal and secure memory is done via migrate_vma_pages(). The reverse movement is driven via pagemap_ops.migrate_to_ram(). The page-in or page-out requests from UV will come to HV as hcalls and HV will call back into UV via uvcalls to satisfy these page requests. These patches are against hmm.git (https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=hmm) plus Claudio Carvalho's base ultravisor enablement patches that are present in Michael Ellerman's tree (https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=topic/ppc-kvm) These patches along with Claudio's above patches are required to run secure pseries guests on KVM. This patchset is based on hmm.git because hmm.git has migrate_vma cleanup and not-device memremap_pages patchsets that are required by this patchset. Changes in v8 ============= - s/kvmppc_devm/kvmppc_uvmem - Carrying Suraj's patch that defines bit positions for different rmap functions from Paul's kvm-next branch. Added KVMPPC_RMAP_UVMEM_PFN to this patch. - No need to use irqsave version of spinlock to protect pfn bitmap - mmap_sem and srcu_lock reversal in page-in/page-out so that we have uniform locking semantics in page-in, page-out, fault and reset paths. This also matches with other usages of the same two locks in powerpc code. - kvmppc_uvmem_free_memslot_pfns() needs kvm srcu read lock. - Addressed all the review feedback from Christoph and Sukadev. - Dropped kvmppc_rmap_is_devm_pfn() and introduced kvmppc_rmap_type() - Bail out early if page-in request comes for an already paged-in page - kvmppc_uvmem_pfn_lock re-arrangement - Check for failure from gfn_to_memslot in kvmppc_h_svm_page_in - Consolidate migrate_vma setup and related code into two helpers kvmppc_svm_page_in/out. - Use NUMA_NO_NODE in memremap_pages() instead of -1 - Removed externs in declarations - Ensure *rmap assignment gets cleared in the error case in kvmppc_uvmem_get_page() - A few other code cleanups v7: https://lists.ozlabs.org/pipermail/linuxppc-dev/2019-August/195631.html Anshuman Khandual (1): KVM: PPC: Ultravisor: Add PPC_UV config option Bharata B Rao (6): kvmppc: Movement of pages between normal and secure memory kvmppc: Shared pages support for secure guests kvmppc: H_SVM_INIT_START and H_SVM_INIT_DONE hcalls kvmppc: Handle memory plug/unplug to secure VM kvmppc: Radix changes for secure guest kvmppc: Support reset of secure guest Suraj Jitindar Singh (1): KVM: PPC: Book3S HV: Define usage types for rmap array in guest memslot Documentation/virt/kvm/api.txt | 19 + arch/powerpc/Kconfig | 17 + arch/powerpc/include/asm/hvcall.h | 9 + arch/powerpc/include/asm/kvm_book3s_uvmem.h | 48 ++ arch/powerpc/include/asm/kvm_host.h | 56 +- arch/powerpc/include/asm/kvm_ppc.h | 2 + arch/powerpc/include/asm/ultravisor-api.h | 6 + arch/powerpc/include/asm/ultravisor.h | 36 ++ arch/powerpc/kvm/Makefile | 3 + arch/powerpc/kvm/book3s_64_mmu_radix.c | 22 + arch/powerpc/kvm/book3s_hv.c | 121 ++++ arch/powerpc/kvm/book3s_hv_rm_mmu.c | 2 +- arch/powerpc/kvm/book3s_hv_uvmem.c | 604 ++++++++++++++++++++ arch/powerpc/kvm/powerpc.c | 12 + include/uapi/linux/kvm.h | 1 + 15 files changed, 953 insertions(+), 5 deletions(-) create mode 100644 arch/powerpc/include/asm/kvm_book3s_uvmem.h create mode 100644 arch/powerpc/kvm/book3s_hv_uvmem.c -- 2.21.0
