Migrate non-migrated pages of a SVM.
Subsystems (3)
v3 cover Migrate non-migrated pages of a SVM.
The time taken to switch a VM to Secure-VM, increases by the size of the VM. A 100GB VM takes about 7minutes. This is unacceptable. This linear increase is caused by a suboptimal behavior by the Ultravisor and the Hypervisor. The Ultravisor unnecessarily migrates all the GFN of the VM from normal-memory to secure-memory. It has to just migrate the necessary and sufficient GFNs.
However when the optimization is incorporated in the Ultravisor, the Hypervisor starts misbehaving. The Hypervisor has a inbuilt assumption that the Ultravisor will explicitly request to migrate, each and every GFN of the VM. If only necessary and sufficient GFNs are requested for migration, the Hypervisor continues to manage the remaining GFNs as normal GFNs. This leads of memory corruption, manifested consistently when the SVM reboots.
The same is true, when a memory slot is hotplugged into a SVM. The Hypervisor expects the ultravisor to request migration of all GFNs to secure-GFN. But the hypervisor cannot handle any H_SVM_PAGE_IN requests from the Ultravisor, done in the context of UV_REGISTER_MEM_SLOT ucall. This problem manifests as random errors in the SVM, when a memory-slot is hotplugged.
This patch series automatically migrates the non-migrated pages of a SVM,
and thus solves the problem.
Testing: Passed rigorous testing using various sized SVMs.
Changelog:
v3: . Optimized the page-migration retry-logic.
. Relax and relinquish the cpu regularly while bulk migrating
the non-migrated pages. This issue was causing soft-lockups. Fixed it.
. Added a new patch, to retry page-migration a couple of times
before returning H_BUSY in H_SVM_PAGE_IN. This issue was seen a few times in a 24hour continuous reboot test of the SVMs.
v2: . fixed a bug observed by Laurent. The state of the GFN's associated
with Secure-VMs were not reset during memslot flush.
. Re-organized the code, for easier review.
. Better description of the patch series.
v1: fixed a bug observed by Bharata. Pages that where paged-in and later paged-out must also be skipped from migration during H_SVM_INIT_DONE.
Laurent Dufour (1):
KVM: PPC: Book3S HV: migrate hot plugged memory
Ram Pai (4):
KVM: PPC: Book3S HV: Disable page merging in H_SVM_INIT_START
KVM: PPC: Book3S HV: track the state GFNs associated with secure VMs
KVM: PPC: Book3S HV: migrate remaining normal-GFNs to secure-GFNs in
H_SVM_INIT_DONE
KVM: PPC: Book3S HV: retry page migration before erroring-out
H_SVM_PAGE_IN
Documentation/powerpc/ultravisor.rst | 3 + arch/powerpc/include/asm/kvm_book3s_uvmem.h | 2 + arch/powerpc/kvm/book3s_hv.c | 10 +- arch/powerpc/kvm/book3s_hv_uvmem.c | 487 ++++++++++++++++++++++++---- 4 files changed, 429 insertions(+), 73 deletions(-)
Signature · 1 line
1.8.3.1
PATCH v3 1/5 KVM: PPC: Book3S HV: Disable page merging in H_SVM_INIT_START
Merging of pages associated with each memslot of a SVM is disabled the page is migrated in H_SVM_PAGE_IN handler.
This operation should have been done much earlier; the moment the VM is initiated for secure-transition. Delaying this operation, increases the probability for those pages to acquire new references , making it impossible to migrate those pages in H_SVM_PAGE_IN handler.
Disable page-migration in H_SVM_INIT_START handling.
--- arch/powerpc/kvm/book3s_hv_uvmem.c | 96 +++++++++++++++++++++++++++++--------- 1 file changed, 74 insertions(+), 22 deletions(-)
arch/powerpc/kvm/book3s_hv_uvmem.c +74 -22
@@ -211,6 +211,65 @@ static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm,return false; } +static int kvmppc_memslot_page_merge (struct kvm *kvm, +struct kvm_memory_slot *memslot,bool merge) +{ +unsigned long gfn = memslot->base_gfn; +unsigned long end, start =gfn_to_hva (kvm, gfn); +int ret =0 ; +struct vm_area_struct *vma; +int merge_flag = (merge) ?MADV_MERGEABLE :MADV_UNMERGEABLE ; + +if (kvm_is_error_hva (start)) +return H_STATE ; + + end = start + (memslot->npages <<PAGE_SHIFT ); + +down_write (&kvm->mm->mmap_sem); +do { + vma =find_vma_intersection (kvm->mm, start, end); +if (!vma) { + ret =H_STATE ; +break ; + } + ret =ksm_madvise (vma, vma->vm_start, vma->vm_end, + merge_flag, &vma->vm_flags); +if (ret) { + ret =H_STATE ; +break ; + } + start = vma->vm_end +1 ; + }while (end > vma->vm_end); + +up_write (&kvm->mm->mmap_sem); +return ret; +} + +static int __kvmppc_page_merge (struct kvm *kvm,bool merge) +{ +struct kvm_memslots *slots; +struct kvm_memory_slot *memslot; +int ret =0 ; + + slots =kvm_memslots (kvm); +kvm_for_each_memslot (memslot, slots) { + ret =kvmppc_memslot_page_merge (kvm, memslot, merge); +if (ret) +break ; + } +return ret; +} + +static inline int kvmppc_disable_page_merge (struct kvm *kvm) +{ +return __kvmppc_page_merge (kvm, false); +} + +static inline int kvmppc_enable_page_merge (struct kvm *kvm) +{ +return __kvmppc_page_merge (kvm, true); +} +unsigned long kvmppc_h_svm_init_start (struct kvm *kvm) {struct kvm_memslots *slots;
@@ -232,11 +291,18 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)return H_AUTHORITY ; srcu_idx =srcu_read_lock (&kvm->srcu); + +/* disable page-merging for all memslot */ + ret =kvmppc_disable_page_merge (kvm); +if (ret) + goto out; + +/* register the memslot */ slots =kvm_memslots (kvm);kvm_for_each_memslot (memslot, slots) {if (kvmppc_uvmem_slot_init (kvm, memslot)) { ret =H_PARAMETER ; - goto out; +break ; } ret = uv_register_mem_slot(kvm->arch.lpid, memslot->base_gfn << PAGE_SHIFT,
@@ -245,9 +311,12 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)if (ret <0 ) {kvmppc_uvmem_slot_free (kvm, memslot); ret =H_PARAMETER ; - goto out; +break ; } } + +if (ret) +kvmppc_enable_page_merge (kvm); out:srcu_read_unlock (&kvm->srcu, srcu_idx);return ret;
@@ -384,7 +453,7 @@ static struct page *kvmppc_uvmem_get_page(unsigned long gpa, struct kvm *kvm)*/ static int kvmppc_svm_page_in (struct vm_area_struct *vma,unsigned long start,unsigned long end,unsigned long gpa,struct kvm *kvm, -unsigned long page_shift,bool *downgrade) +unsigned long page_shift) {unsigned long src_pfn, dst_pfn =0 ;struct migrate_vma mig;
@@ -400,18 +469,6 @@ static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, mig.src = &src_pfn; mig.dst = &dst_pfn; -/* -* We come here with mmap_sem write lock held just for -* ksm_madvise(), otherwise we only need read mmap_sem. -* Hence downgrade to read lock once ksm_madvise() is done. -*/ - ret =ksm_madvise (vma, vma->vm_start, vma->vm_end, -MADV_UNMERGEABLE , &vma->vm_flags); -downgrade_write (&kvm->mm->mmap_sem); - *downgrade = true; -if (ret) -return ret; - ret =migrate_vma_setup (&mig);if (ret)return ret;
@@ -503,7 +560,6 @@ unsigned long kvmppc_h_svm_page_in(struct kvm *kvm, unsigned long gpa,unsigned long flags, unsigned long page_shift) { - bool downgrade = false; unsigned long start, end;struct vm_area_struct *vma;int srcu_idx;
@@ -540,16 +596,12 @@ unsigned long kvmppc_h_svm_page_in(struct kvm *kvm, unsigned long gpa,if (!vma || vma->vm_start > start || vma->vm_end < end) goto out_unlock; -if (!kvmppc_svm_page_in (vma, start, end, gpa, kvm, page_shift, - &downgrade)) +if (!kvmppc_svm_page_in (vma, start, end, gpa, kvm, page_shift)) ret =H_SUCCESS ; out_unlock:mutex_unlock (&kvm->arch.uvmem_lock); out: -if (downgrade) -up_read (&kvm->mm->mmap_sem); -else -up_write (&kvm->mm->mmap_sem); +up_write (&kvm->mm->mmap_sem);srcu_read_unlock (&kvm->srcu, srcu_idx);return ret; }
Signature · 1 line
1.8.3.1
Re: [v3 1/5] KVM: PPC: Book3S HV: Disable page merging in H_SVM_INIT_START
Quoted 9 lines · Ram Pai
Merging of pages associated with each memslot of a SVM is disabled the page is migrated in
H_SVM_PAGE_INhandler.This operation should have been done much earlier; the moment the VM is initiated for secure-transition. Delaying this operation, increases the probability for those pages to acquire new references , making it impossible to migrate those pages in
H_SVM_PAGE_INhandler.Disable page-migration in
H_SVM_INIT_STARThandling.
While it is a good idea to disable KSM merging for all VMAs during H_SVM_INIT_START, I am curious if you did observe an actual case of ksm_madvise() failing which resulted in subsequent H_SVM_PAGE_IN failing to migrate?
Quoted 15 lines
Signed-off-by Ram Pai <[email protected]>--- arch/powerpc/kvm/book3s_hv_uvmem.c | 96 +++++++++++++++++++++++++++++--------- 1 file changed, 74 insertions(+), 22 deletions(-)arch/powerpc/kvm/book3s_hv_uvmem.c +1
-0@@ -211,6 +211,65 @@ static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm,return false; } +static int kvmppc_memslot_page_merge(struct kvm *kvm,
arch/powerpc/kvm/book3s_hv_uvmem.c static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm, · line 224
Quoted 10 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +10
-0+ struct kvm_memory_slot *memslot, bool merge) +{ +unsigned long gfn = memslot->base_gfn; +unsigned long end, start =gfn_to_hva (kvm, gfn); +int ret =0 ; +struct vm_area_struct *vma; +int merge_flag = (merge) ?MADV_MERGEABLE :MADV_UNMERGEABLE ; + +if (kvm_is_error_hva (start)) +return H_STATE ;
This and other cases below seem to be a new return value from H_SVM_INIT_START. May be update the documentation too along with this patch?
arch/powerpc/kvm/book3s_hv_uvmem.c static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm, · line 228
Quoted 4 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +4
-0+ + end = start + (memslot->npages <<PAGE_SHIFT ); + +down_write (&kvm->mm->mmap_sem);
When you rebase the patches against latest upstream you may want to replace the above and other instances by mmap_write/read_lock().
Quoted 68 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +52
-1+do { + vma =find_vma_intersection (kvm->mm, start, end); +if (!vma) { + ret =H_STATE ; +break ; + } + ret =ksm_madvise (vma, vma->vm_start, vma->vm_end, + merge_flag, &vma->vm_flags); +if (ret) { + ret =H_STATE ; +break ; + } + start = vma->vm_end +1 ; + }while (end > vma->vm_end); + +up_write (&kvm->mm->mmap_sem); +return ret; +} + +static int __kvmppc_page_merge (struct kvm *kvm,bool merge) +{ +struct kvm_memslots *slots; +struct kvm_memory_slot *memslot; +int ret =0 ; + + slots =kvm_memslots (kvm); +kvm_for_each_memslot (memslot, slots) { + ret =kvmppc_memslot_page_merge (kvm, memslot, merge); +if (ret) +break ; + } +return ret; +} + +static inline int kvmppc_disable_page_merge (struct kvm *kvm) +{ +return __kvmppc_page_merge (kvm, false); +} + +static inline int kvmppc_enable_page_merge (struct kvm *kvm) +{ +return __kvmppc_page_merge (kvm, true); +} +unsigned long kvmppc_h_svm_init_start (struct kvm *kvm) {struct kvm_memslots *slots;@@ -232,11 +291,18 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)return H_AUTHORITY ; srcu_idx =srcu_read_lock (&kvm->srcu); + +/* disable page-merging for all memslot */ + ret =kvmppc_disable_page_merge (kvm); +if (ret) + goto out; + +/* register the memslot */ slots =kvm_memslots (kvm);kvm_for_each_memslot (memslot, slots) {if (kvmppc_uvmem_slot_init (kvm, memslot)) { ret =H_PARAMETER ; - goto out; +break ; } ret = uv_register_mem_slot(kvm->arch.lpid, memslot->base_gfn << PAGE_SHIFT,
arch/powerpc/kvm/book3s_hv_uvmem.c unsigned long kvmppc_h_svm_init_start(struct kvm *kvm) · line 319
Quoted 10 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +4
-1@@ -245,9 +311,12 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)if (ret <0 ) {kvmppc_uvmem_slot_free (kvm, memslot); ret =H_PARAMETER ; - goto out; +break ; } } + +if (ret) +kvmppc_enable_page_merge (kvm);
Is there any use of enabling KSM merging in the failure path here? Won't UV terminate the VM if H_SVM_INIT_START fails? If there is no need, you can do away with some extra routines above.
Quoted 13 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +1
-1out:srcu_read_unlock (&kvm->srcu, srcu_idx);return ret;@@ -384,7 +453,7 @@ static struct page *kvmppc_uvmem_get_page(unsigned long gpa, struct kvm *kvm)*/ static int kvmppc_svm_page_in (struct vm_area_struct *vma,unsigned long start,unsigned long end,unsigned long gpa,struct kvm *kvm, -unsigned long page_shift,bool *downgrade) +unsigned long page_shift) {unsigned long src_pfn, dst_pfn =0 ;struct migrate_vma mig;
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 409
Quoted 10 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +0
-7@@ -400,18 +469,6 @@ static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, mig.src = &src_pfn; mig.dst = &dst_pfn; -/* -* We come here with mmap_sem write lock held just for -* ksm_madvise(), otherwise we only need read mmap_sem. -* Hence downgrade to read lock once ksm_madvise() is done. -*/ - ret =ksm_madvise (vma, vma->vm_start, vma->vm_end, -MADV_UNMERGEABLE , &vma->vm_flags);
I haven't seen the subsequent patches yet, but guess you are taking care of disabling KSM mering for hot-plugged memory too.
Regards,
Bharata.
Re: [v3 1/5] KVM: PPC: Book3S HV: Disable page merging in H_SVM_INIT_START
Quoted 9 lines · Bharata B Rao
Quoted 8 lines · Ram Pai
Merging of pages associated with each memslot of a SVM is disabled the page is migrated in
H_SVM_PAGE_INhandler.This operation should have been done much earlier; the moment the VM is initiated for secure-transition. Delaying this operation, increases the probability for those pages to acquire new references , making it impossible to migrate those pages in
H_SVM_PAGE_INhandler.
Quoted 6 lines
Quoted 1 line
Disable page-migration in
H_SVM_INIT_STARThandling.While it is a good idea to disable KSM merging for all VMAs during
H_SVM_INIT_START, I am curious if you did observe an actual case ofksm_madvise()failing which resulted in subsequentH_SVM_PAGE_INfailing to migrate?
No. I did not find any ksm_madvise() failing. But it did not make sense to ksm_madvise() everytime a page_in was requested. Hence i proposed this patch. H_SVM_INIT_START is the right place for ksm_advise().
Quoted 15 lines
Quoted 15 lines
Signed-off-by Ram Pai <[email protected]>--- arch/powerpc/kvm/book3s_hv_uvmem.c | 96 +++++++++++++++++++++++++++++--------- 1 file changed, 74 insertions(+), 22 deletions(-)arch/powerpc/kvm/book3s_hv_uvmem.c +0
-0@@ -211,6 +211,65 @@ static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm,return false; }
Quoted 15 lines
arch/powerpc/kvm/book3s_hv_uvmem.c static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm, · line 224
Quoted 11 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +11
-0+static int kvmppc_memslot_page_merge (struct kvm *kvm, +struct kvm_memory_slot *memslot,bool merge) +{ +unsigned long gfn = memslot->base_gfn; +unsigned long end, start =gfn_to_hva (kvm, gfn); +int ret =0 ; +struct vm_area_struct *vma; +int merge_flag = (merge) ?MADV_MERGEABLE :MADV_UNMERGEABLE ; + +if (kvm_is_error_hva (start)) +return H_STATE ;This and other cases below seem to be a new return value from
H_SVM_INIT_START. May be update the documentation too along with this patch?
ok.
Quoted 8 lines
arch/powerpc/kvm/book3s_hv_uvmem.c static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm, · line 228
Quoted 5 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +4
-0+ + end = start + (memslot->npages <<PAGE_SHIFT ); + +down_write (&kvm->mm->mmap_sem);When you rebase the patches against latest upstream you may want to replace the above and other instances by mmap_write/read_lock().
ok.
Quoted 75 lines
Quoted 75 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +53
-2+do { + vma =find_vma_intersection (kvm->mm, start, end); +if (!vma) { + ret =H_STATE ; +break ; + } + ret =ksm_madvise (vma, vma->vm_start, vma->vm_end, + merge_flag, &vma->vm_flags); +if (ret) { + ret =H_STATE ; +break ; + } + start = vma->vm_end +1 ; + }while (end > vma->vm_end); + +up_write (&kvm->mm->mmap_sem); +return ret; +} + +static int __kvmppc_page_merge (struct kvm *kvm,bool merge) +{ +struct kvm_memslots *slots; +struct kvm_memory_slot *memslot; +int ret =0 ; + + slots =kvm_memslots (kvm); +kvm_for_each_memslot (memslot, slots) { + ret =kvmppc_memslot_page_merge (kvm, memslot, merge); +if (ret) +break ; + } +return ret; +} + +static inline int kvmppc_disable_page_merge (struct kvm *kvm) +{ +return __kvmppc_page_merge (kvm, false); +} + +static inline int kvmppc_enable_page_merge (struct kvm *kvm) +{ +return __kvmppc_page_merge (kvm, true); +} +unsigned long kvmppc_h_svm_init_start (struct kvm *kvm) {struct kvm_memslots *slots;@@ -232,11 +291,18 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)return H_AUTHORITY ; srcu_idx =srcu_read_lock (&kvm->srcu); + +/* disable page-merging for all memslot */ + ret =kvmppc_disable_page_merge (kvm); +if (ret) + goto out; + +/* register the memslot */ slots =kvm_memslots (kvm);kvm_for_each_memslot (memslot, slots) {if (kvmppc_uvmem_slot_init (kvm, memslot)) { ret =H_PARAMETER ; - goto out; +break ; } ret = uv_register_mem_slot(kvm->arch.lpid, memslot->base_gfn << PAGE_SHIFT,@@ -245,9 +311,12 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)if (ret <0 ) {kvmppc_uvmem_slot_free (kvm, memslot); ret =H_PARAMETER ; - goto out; +break ; }
Quoted 8 lines
arch/powerpc/kvm/book3s_hv_uvmem.c unsigned long kvmppc_h_svm_init_start(struct kvm *kvm) · line 319
Quoted 4 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +3
-0} + +if (ret) +kvmppc_enable_page_merge (kvm);Is there any use of enabling KSM merging in the failure path here? Won't UV terminate the VM if
H_SVM_INIT_STARTfails? If there is no need, you can do away with some extra routines above.
UV will terminate it. But I did not want to tie that assumption into this function.
Quoted 17 lines
Quoted 17 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +1
-1out:srcu_read_unlock (&kvm->srcu, srcu_idx);return ret;@@ -384,7 +453,7 @@ static struct page *kvmppc_uvmem_get_page(unsigned long gpa, struct kvm *kvm)*/ static int kvmppc_svm_page_in (struct vm_area_struct *vma,unsigned long start,unsigned long end,unsigned long gpa,struct kvm *kvm, -unsigned long page_shift,bool *downgrade) +unsigned long page_shift) {unsigned long src_pfn, dst_pfn =0 ;struct migrate_vma mig;@@ -400,18 +469,6 @@ static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, mig.src = &src_pfn; mig.dst = &dst_pfn;
Quoted 10 lines
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 409
Quoted 7 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +0
-7-/* -* We come here with mmap_sem write lock held just for -* ksm_madvise(), otherwise we only need read mmap_sem. -* Hence downgrade to read lock once ksm_madvise() is done. -*/ - ret =ksm_madvise (vma, vma->vm_start, vma->vm_end, -MADV_UNMERGEABLE , &vma->vm_flags);I haven't seen the subsequent patches yet, but guess you are taking care of disabling KSM mering for hot-plugged memory too.
No. This is a good catch. The hotplugged memory patch needs to disable KSM aswell.
RP
Re: [v3 1/5] KVM: PPC: Book3S HV: Disable page merging in H_SVM_INIT_START
Quoted 12 lines · Ram Pai
Quoted 11 lines · Bharata B Rao
Quoted 9 lines · Ram Pai
Merging of pages associated with each memslot of a SVM is disabled the page is migrated in
H_SVM_PAGE_INhandler.This operation should have been done much earlier; the moment the VM is initiated for secure-transition. Delaying this operation, increases the probability for those pages to acquire new references , making it impossible to migrate those pages in
H_SVM_PAGE_INhandler.Disable page-migration in
H_SVM_INIT_STARThandling.
Quoted 8 lines
Quoted 4 lines
While it is a good idea to disable KSM merging for all VMAs during
H_SVM_INIT_START, I am curious if you did observe an actual case ofksm_madvise()failing which resulted in subsequentH_SVM_PAGE_INfailing to migrate?No. I did not find any
ksm_madvise()failing. But it did not make sense toksm_madvise()everytime apage_inwas requested. Hence i proposed this patch.H_SVM_INIT_STARTis the right place forksm_advise().
Indeed yes. Then you may want to update the description which currently seems to imply that this change is being done to avoid issues arising out of delayed KSM unmerging advice.
Quoted 129 lines
Quoted 16 lines
Quoted 16 lines
Signed-off-by Ram Pai <[email protected]>--- arch/powerpc/kvm/book3s_hv_uvmem.c | 96 +++++++++++++++++++++++++++++--------- 1 file changed, 74 insertions(+), 22 deletions(-)arch/powerpc/kvm/book3s_hv_uvmem.c +0
-0@@ -211,6 +211,65 @@ static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm,return false; }Quoted 15 lines
arch/powerpc/kvm/book3s_hv_uvmem.c static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm, · line 224
Quoted 11 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +11
-0+static int kvmppc_memslot_page_merge (struct kvm *kvm, +struct kvm_memory_slot *memslot,bool merge) +{ +unsigned long gfn = memslot->base_gfn; +unsigned long end, start =gfn_to_hva (kvm, gfn); +int ret =0 ; +struct vm_area_struct *vma; +int merge_flag = (merge) ?MADV_MERGEABLE :MADV_UNMERGEABLE ; + +if (kvm_is_error_hva (start)) +return H_STATE ;This and other cases below seem to be a new return value from
H_SVM_INIT_START. May be update the documentation too along with this patch?ok.
Quoted 8 lines
arch/powerpc/kvm/book3s_hv_uvmem.c static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm, · line 228
Quoted 5 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +4
-0+ + end = start + (memslot->npages <<PAGE_SHIFT ); + +down_write (&kvm->mm->mmap_sem);When you rebase the patches against latest upstream you may want to replace the above and other instances by mmap_write/read_lock().
ok.
Quoted 75 lines
Quoted 75 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +53
-2+do { + vma =find_vma_intersection (kvm->mm, start, end); +if (!vma) { + ret =H_STATE ; +break ; + } + ret =ksm_madvise (vma, vma->vm_start, vma->vm_end, + merge_flag, &vma->vm_flags); +if (ret) { + ret =H_STATE ; +break ; + } + start = vma->vm_end +1 ; + }while (end > vma->vm_end); + +up_write (&kvm->mm->mmap_sem); +return ret; +} + +static int __kvmppc_page_merge (struct kvm *kvm,bool merge) +{ +struct kvm_memslots *slots; +struct kvm_memory_slot *memslot; +int ret =0 ; + + slots =kvm_memslots (kvm); +kvm_for_each_memslot (memslot, slots) { + ret =kvmppc_memslot_page_merge (kvm, memslot, merge); +if (ret) +break ; + } +return ret; +} + +static inline int kvmppc_disable_page_merge (struct kvm *kvm) +{ +return __kvmppc_page_merge (kvm, false); +} + +static inline int kvmppc_enable_page_merge (struct kvm *kvm) +{ +return __kvmppc_page_merge (kvm, true); +} +unsigned long kvmppc_h_svm_init_start (struct kvm *kvm) {struct kvm_memslots *slots;@@ -232,11 +291,18 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)return H_AUTHORITY ; srcu_idx =srcu_read_lock (&kvm->srcu); + +/* disable page-merging for all memslot */ + ret =kvmppc_disable_page_merge (kvm); +if (ret) + goto out; + +/* register the memslot */ slots =kvm_memslots (kvm);kvm_for_each_memslot (memslot, slots) {if (kvmppc_uvmem_slot_init (kvm, memslot)) { ret =H_PARAMETER ; - goto out; +break ; } ret = uv_register_mem_slot(kvm->arch.lpid, memslot->base_gfn << PAGE_SHIFT,@@ -245,9 +311,12 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)if (ret <0 ) {kvmppc_uvmem_slot_free (kvm, memslot); ret =H_PARAMETER ; - goto out; +break ; }Quoted 8 lines
arch/powerpc/kvm/book3s_hv_uvmem.c unsigned long kvmppc_h_svm_init_start(struct kvm *kvm) · line 319
Quoted 4 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +3
-0} + +if (ret) +kvmppc_enable_page_merge (kvm);Is there any use of enabling KSM merging in the failure path here? Won't UV terminate the VM if
H_SVM_INIT_STARTfails? If there is no need, you can do away with some extra routines above.
Quoted 2 lines
UV will terminate it. But I did not want to tie that assumption into this function.
Hmm ok, but having code around which isn't expected to be executed at all was my concern.
Regards,
Bharata.
PATCH v3 2/5 KVM: PPC: Book3S HV: track the state of GFNs associated with secure VMs
In reply to Ram PaiDuring the life of SVM, its GFNs transition through normal, secure and shared states. Since the kernel does not track GFNs that are shared, it is not possible to disambiguate a shared GFN from a GFN whose PFN has not yet been migrated to a secure-PFN. Also it is not possible to disambiguate a secure-GFN from a GFN whose GFN has been pagedout from the ultravisor.
The ability to identify the state of a GFN is needed to skip migration of its PFN to secure-PFN during ESM transition.
The code is re-organized to track the states of a GFN as explained below.
************************************************************************
1. States of a GFN
---------------
The GFN can be in one of the following states.
(a) Secure - The GFN is secure. The GFN is associated with a Secure VM, the contents of the GFN is not accessible to the Hypervisor. This GFN can be backed by a secure-PFN, or can be backed by a normal-PFN with contents encrypted. The former is true when the GFN is paged-in into the ultravisor. The latter is true when the GFN is paged-out of the ultravisor.
(b) Shared - The GFN is shared. The GFN is associated with a a secure VM. The contents of the GFN is accessible to Hypervisor. This GFN is backed by a normal-PFN and its content is un-encrypted.
(c) Normal - The GFN is a normal. The GFN is associated with a normal VM. The contents of the GFN is accesible to the Hypervisor. Its content is never encrypted.
2. States of a VM.
---------------
(a) Normal VM: A VM whose contents are always accessible to the hypervisor. All its GFNs are normal-GFNs.
(b) Secure VM: A VM whose contents are not accessible to the hypervisor without the VM's consent. Its GFNs are either Shared-GFN or Secure-GFNs.
(c) Transient VM: A Normal VM that is transitioning to secure VM. The transition starts on successful return of H_SVM_INIT_START, and ends on successful return of H_SVM_INIT_DONE. This transient VM, can have GFNs in any of the three states; i.e Secure-GFN, Shared-GFN,
and Normal-GFN. The VM never executes in this state
in supervisor-mode.
3. Memory slot State.
------------------
The state of a memory slot mirrors the state of the VM the memory slot is associated with.
4. VM State transition.
--------------------
A VM always starts in Normal Mode.
H_SVM_INIT_START moves the VM into transient state. During this time the Ultravisor may request some of its GFNs to be shared or secured. So its GFNs can be in one of the three GFN states.
H_SVM_INIT_DONE moves the VM entirely from transient state to secure-state. At this point any left-over normal-GFNs are transitioned to Secure-GFN.
H_SVM_INIT_ABORT moves the transient VM back to normal VM. All its GFNs are moved to Normal-GFNs.
UV_TERMINATE transitions the secure-VM back to normal-VM. All the secure-GFN and shared-GFNs are tranistioned to normal-GFN
Note: The contents of the normal-GFN is undefined at this point.
5. GFN state implementation:
-------------------------
Secure GFN is associated with a secure-PFN; also called uvmem_pfn, when the GFN is paged-in. Its pfn[] has KVMPPC_GFN_UVMEM_PFN flag set, and contains the value of the secure-PFN.
It is associated with a normal-PFN; also called mem_pfn, when the GFN is pagedout. Its pfn[] has KVMPPC_GFN_MEM_PFN flag set. The value of the normal-PFN is not tracked.
Shared GFN is associated with a normal-PFN. Its pfn[] has KVMPPC_UVMEM_SHARED_PFN flag set. The value of the normal-PFN is not tracked.
Normal GFN is associated with normal-PFN. Its pfn[] has no flag set. The value of the normal-PFN is not tracked.
6. Life cycle of a GFN
-------------------- -------------------------------------------------------------- | | Share | Unshare | SVM |H_SVM_INIT_DONE| | |operation |operation | abort/ | | | | | | terminate | | ------------------------------------------------------------- | | | | | | | Secure | Shared | Secure |Normal |Secure | | | | | | | | Shared | Shared | Secure |Normal |Shared | | | | | | | | Normal | Shared | Secure |Normal |Secure |
--------------------------------------------------------------
7. Life cycle of a VM
-------------------- -------------------------------------------------------------------- | | start | H_SVM_ |H_SVM_ |H_SVM_ |UV_SVM_ | | | VM |INIT_START|INIT_DONE|INIT_ABORT |TERMINATE | | | | | | | | --------- ---------------------------------------------------------- | | | | | | | | Normal | Normal | Transient|Error |Error |Normal | | | | | | | | | Secure | Error | Error |Error |Error |Normal | | | | | | | | |Transient| N/A | Error |Secure |Normal |Normal |
--------------------------------------------------------------------
************************************************************************
--- arch/powerpc/kvm/book3s_hv_uvmem.c | 187 +++++++++++++++++++++++++++++++++---- 1 file changed, 168 insertions(+), 19 deletions(-)
arch/powerpc/kvm/book3s_hv_uvmem.c +168 -19
@@ -98,7 +98,127 @@static unsigned long *kvmppc_uvmem_bitmap;static DEFINE_SPINLOCK (kvmppc_uvmem_bitmap_lock); -#define KVMPPC_UVMEM_PFN (1UL << 63) +/* +* States of a GFN +* --------------- +* The GFN can be in one of the following states. +* +* (a) Secure - The GFN is secure. The GFN is associated with +* a Secure VM, the contents of the GFN is not accessible +* to the Hypervisor. This GFN can be backed by a secure-PFN, +* or can be backed by a normal-PFN with contents encrypted. +* The former is true when the GFN is paged-in into the +* ultravisor. The latter is true when the GFN is paged-out +* of the ultravisor. +* +* (b) Shared - The GFN is shared. The GFN is associated with a +* a secure VM. The contents of the GFN is accessible to +* Hypervisor. This GFN is backed by a normal-PFN and its +* content is un-encrypted. +* +* (c) Normal - The GFN is a normal. The GFN is associated with +* a normal VM. The contents of the GFN is accesible to +* the Hypervisor. Its content is never encrypted. +* +* States of a VM. +* --------------- +* +* Normal VM: A VM whose contents are always accessible to +* the hypervisor. All its GFNs are normal-GFNs. +* +* Secure VM: A VM whose contents are not accessible to the +* hypervisor without the VM's consent. Its GFNs are +* either Shared-GFN or Secure-GFNs. +* +* Transient VM: A Normal VM that is transitioning to secure VM. +* The transition starts on successful return of +* H_SVM_INIT_START, and ends on successful return +* of H_SVM_INIT_DONE. This transient VM, can have GFNs +* in any of the three states; i.e Secure-GFN, Shared-GFN, +* and Normal-GFN. The VM never executes in this state +* in supervisor-mode. +* +* Memory slot State. +* ----------------------------- +* The state of a memory slot mirrors the state of the +* VM the memory slot is associated with. +* +* VM State transition. +* -------------------- +* +* A VM always starts in Normal Mode. +* +* H_SVM_INIT_START moves the VM into transient state. During this +* time the Ultravisor may request some of its GFNs to be shared or +* secured. So its GFNs can be in one of the three GFN states. +* +* H_SVM_INIT_DONE moves the VM entirely from transient state to +* secure-state. At this point any left-over normal-GFNs are +* transitioned to Secure-GFN. +* +* H_SVM_INIT_ABORT moves the transient VM back to normal VM. +* All its GFNs are moved to Normal-GFNs. +* +* UV_TERMINATE transitions the secure-VM back to normal-VM. All +* the secure-GFN and shared-GFNs are tranistioned to normal-GFN +* Note: The contents of the normal-GFN is undefined at this point. +* +* GFN state implementation: +* ------------------------- +* +* Secure GFN is associated with a secure-PFN; also called uvmem_pfn, +* when the GFN is paged-in. Its pfn[] has KVMPPC_GFN_UVMEM_PFN flag +* set, and contains the value of the secure-PFN. +* It is associated with a normal-PFN; also called mem_pfn, when +* the GFN is pagedout. Its pfn[] has KVMPPC_GFN_MEM_PFN flag set. +* The value of the normal-PFN is not tracked. +* +* Shared GFN is associated with a normal-PFN. Its pfn[] has +* KVMPPC_UVMEM_SHARED_PFN flag set. The value of the normal-PFN +* is not tracked. +* +* Normal GFN is associated with normal-PFN. Its pfn[] has +* no flag set. The value of the normal-PFN is not tracked. +* +* Life cycle of a GFN +* -------------------- +* +* -------------------------------------------------------------- +* | | Share | Unshare | SVM |H_SVM_INIT_DONE| +* | |operation |operation | abort/ | | +* | | | | terminate | | +* ------------------------------------------------------------- +* | | | | | | +* | Secure | Shared | Secure |Normal |Secure | +* | | | | | | +* | Shared | Shared | Secure |Normal |Shared | +* | | | | | | +* | Normal | Shared | Secure |Normal |Secure | +* -------------------------------------------------------------- +* +* Life cycle of a VM +* -------------------- +* +* -------------------------------------------------------------------- +* | | start | H_SVM_ |H_SVM_ |H_SVM_ |UV_SVM_ | +* | | VM |INIT_START|INIT_DONE|INIT_ABORT |TERMINATE | +* | | | | | | | +* --------- ---------------------------------------------------------- +* | | | | | | | +* | Normal | Normal | Transient|Error |Error |Normal | +* | | | | | | | +* | Secure | Error | Error |Error |Error |Normal | +* | | | | | | | +* |Transient| N/A | Error |Secure |Normal |Normal | +* -------------------------------------------------------------------- +*/ + +#define KVMPPC_GFN_UVMEM_PFN (1UL << 63) +#define KVMPPC_GFN_MEM_PFN (1UL << 62) +#define KVMPPC_GFN_SHARED (1UL << 61) +#define KVMPPC_GFN_SECURE (KVMPPC_GFN_UVMEM_PFN | KVMPPC_GFN_MEM_PFN) +#define KVMPPC_GFN_FLAG_MASK (KVMPPC_GFN_SECURE | KVMPPC_GFN_SHARED) +#define KVMPPC_GFN_PFN_MASK (~KVMPPC_GFN_FLAG_MASK)struct kvmppc_uvmem_slot {struct list_head list;
@@ -106,11 +226,11 @@ struct kvmppc_uvmem_slot {unsigned long base_pfn;unsigned long *pfns; }; -struct kvmppc_uvmem_page_pvt {struct kvm *kvm;unsigned long gpa;bool skip_page_out; +bool remove_gfn; };bool kvmppc_uvmem_available (void )
@@ -163,8 +283,8 @@ void kvmppc_uvmem_slot_free(struct kvm *kvm, const struct kvm_memory_slot *slot)mutex_unlock (&kvm->arch.uvmem_lock); } -static void kvmppc_uvmem_pfn_insert (unsigned long gfn,unsigned long uvmem_pfn, -struct kvm *kvm) +static void kvmppc_mark_gfn (unsigned long gfn,struct kvm *kvm, +unsigned long flag,unsigned long uvmem_pfn) {struct kvmppc_uvmem_slot *p;
@@ -172,24 +292,41 @@ static void kvmppc_uvmem_pfn_insert(unsigned long gfn, unsigned long uvmem_pfn,if (gfn >= p->base_pfn && gfn < p->base_pfn + p->nr_pfns) {unsigned long index = gfn - p->base_pfn; - p->pfns[index] = uvmem_pfn |KVMPPC_UVMEM_PFN ; +if (flag =KVMPPC_GFN_UVMEM_PFN ) + p->pfns[index] = uvmem_pfn | flag; +else + p->pfns[index] = flag;return ; } } } -static void kvmppc_uvmem_pfn_remove (unsigned long gfn,struct kvm *kvm) +/* mark the GFN as secure-GFN associated with @uvmem pfn device-PFN. */ +static void kvmppc_gfn_secure_uvmem_pfn (unsigned long gfn, +unsigned long uvmem_pfn,struct kvm *kvm) { -struct kvmppc_uvmem_slot *p; +kvmppc_mark_gfn (gfn, kvm,KVMPPC_GFN_UVMEM_PFN , uvmem_pfn); +} -list_for_each_entry (p, &kvm->arch.uvmem_pfns, list) { -if (gfn >= p->base_pfn && gfn < p->base_pfn + p->nr_pfns) { - p->pfns[gfn - p->base_pfn] =0 ; -return ; - } - } +/* mark the GFN as secure-GFN associated with a memory-PFN. */ +static void kvmppc_gfn_secure_mem_pfn (unsigned long gfn,struct kvm *kvm) +{ +kvmppc_mark_gfn (gfn, kvm,KVMPPC_GFN_MEM_PFN ,0 ); +} + +/* mark the GFN as a shared GFN. */ +static void kvmppc_gfn_shared (unsigned long gfn,struct kvm *kvm) +{ +kvmppc_mark_gfn (gfn, kvm,KVMPPC_GFN_SHARED ,0 ); +} + +/* mark the GFN as a non-existent GFN. */ +static void kvmppc_gfn_remove (unsigned long gfn,struct kvm *kvm) +{ +kvmppc_mark_gfn (gfn, kvm,0 ,0 ); } +/* return true, if the GFN is a secure-GFN backed by a secure-PFN */ static bool kvmppc_gfn_is_uvmem_pfn (unsigned long gfn,struct kvm *kvm,unsigned long *uvmem_pfn) {
@@ -199,10 +336,10 @@ static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm,if (gfn >= p->base_pfn && gfn < p->base_pfn + p->nr_pfns) {unsigned long index = gfn - p->base_pfn; -if (p->pfns[index] &KVMPPC_UVMEM_PFN ) { +if (p->pfns[index] &KVMPPC_GFN_UVMEM_PFN ) {if (uvmem_pfn) *uvmem_pfn = p->pfns[index] & - ~KVMPPC_UVMEM_PFN ; +KVMPPC_GFN_PFN_MASK ;return true; }else return false;
@@ -353,6 +490,7 @@ void kvmppc_uvmem_drop_pages(const struct kvm_memory_slot *free,mutex_lock (&kvm->arch.uvmem_lock);if (!kvmppc_gfn_is_uvmem_pfn (gfn, kvm, &uvmem_pfn)) { +kvmppc_gfn_remove (gfn, kvm);mutex_unlock (&kvm->arch.uvmem_lock);continue ; }
@@ -360,6 +498,7 @@ void kvmppc_uvmem_drop_pages(const struct kvm_memory_slot *free, uvmem_page =pfn_to_page (uvmem_pfn); pvt = uvmem_page->zone_device_data; pvt->skip_page_out = skip_page_out; + pvt->remove_gfn = true;mutex_unlock (&kvm->arch.uvmem_lock); pfn =gfn_to_pfn (kvm, gfn);
@@ -429,7 +568,7 @@ static struct page *kvmppc_uvmem_get_page(unsigned long gpa, struct kvm *kvm) goto out_clear; uvmem_pfn = bit + pfn_first; -kvmppc_uvmem_pfn_insert (gpa >>PAGE_SHIFT , uvmem_pfn, kvm); +kvmppc_gfn_secure_uvmem_pfn (gpa >>PAGE_SHIFT , uvmem_pfn, kvm); pvt->gpa = gpa; pvt->kvm = kvm;
@@ -524,6 +663,7 @@ static unsigned long kvmppc_share_page(struct kvm *kvm, unsigned long gpa, uvmem_page =pfn_to_page (uvmem_pfn); pvt = uvmem_page->zone_device_data; pvt->skip_page_out = true; + pvt->remove_gfn = false; } retry:
@@ -537,12 +677,16 @@ static unsigned long kvmppc_share_page(struct kvm *kvm, unsigned long gpa, uvmem_page =pfn_to_page (uvmem_pfn); pvt = uvmem_page->zone_device_data; pvt->skip_page_out = true; + pvt->remove_gfn = false;kvm_release_pfn_clean (pfn); goto retry; } -if (!uv_page_in (kvm->arch.lpid, pfn << page_shift, gpa,0 , page_shift)) +if (!uv_page_in (kvm->arch.lpid, pfn << page_shift, gpa,0 , + page_shift)) { +kvmppc_gfn_shared (gfn, kvm); ret =H_SUCCESS ; + }kvm_release_pfn_clean (pfn);mutex_unlock (&kvm->arch.uvmem_lock); out:
@@ -598,6 +742,7 @@ unsigned long kvmppc_h_svm_page_in(struct kvm *kvm, unsigned long gpa,if (!kvmppc_svm_page_in (vma, start, end, gpa, kvm, page_shift)) ret =H_SUCCESS ; + out_unlock:mutex_unlock (&kvm->arch.uvmem_lock); out:
@@ -706,7 +851,8 @@ static vm_fault_t kvmppc_uvmem_migrate_to_ram(struct vm_fault *vmf)/* * Release the device PFN back to the pool * -* Gets called when secure page becomes a normal page during H_SVM_PAGE_OUT. +* Gets called when secure GFN tranistions from a secure-PFN +* to a normal PFN during H_SVM_PAGE_OUT. * Gets called with kvm->arch.uvmem_lock held. */ static void kvmppc_uvmem_page_free (struct page *page)
@@ -721,7 +867,10 @@ static void kvmppc_uvmem_page_free(struct page *page) pvt = page->zone_device_data; page->zone_device_data =NULL ; -kvmppc_uvmem_pfn_remove (pvt->gpa >>PAGE_SHIFT , pvt->kvm); +if (pvt->remove_gfn) +kvmppc_gfn_remove (pvt->gpa >>PAGE_SHIFT , pvt->kvm); +else +kvmppc_gfn_secure_mem_pfn (pvt->gpa >>PAGE_SHIFT , pvt->kvm);kfree (pvt); }
Signature · 1 line
1.8.3.1
PATCH v3 3/5 KVM: PPC: Book3S HV: migrate remaining normal-GFNs to secure-GFNs in H_SVM_INIT_DONE
In reply to Ram PaiThe Ultravisor is expected to explicitly call H_SVM_PAGE_IN for all the pages of the SVM before calling H_SVM_INIT_DONE. This causes a huge delay in tranistioning the VM to SVM. The Ultravisor is interested in the pages that contain the kernel, initrd and other important data structures. The rest of the pages contain throw-away content. Hence requesting just the necessary and sufficient pages from the Hypervisor is sufficient.
However if not all pages are requested by the Ultravisor, the Hypervisor continues to consider the GFNs corresponding to the non-requested pages as normal GFNs. This can lead to data-corruption and undefined behavior.
Move all the PFNs associated with the SVM's GFNs to secure-PFNs, in H_SVM_INIT_DONE. Skip the GFNs that are already Paged-in or Shared or Paged-in followed by a Paged-out.
--- Documentation/powerpc/ultravisor.rst | 2 + arch/powerpc/include/asm/kvm_book3s_uvmem.h | 2 + arch/powerpc/kvm/book3s_hv_uvmem.c | 166 +++++++++++++++++++++++++--- 3 files changed, 156 insertions(+), 14 deletions(-)
Documentation/powerpc/ultravisor.rst +2 -0
@@ -933,6 +933,8 @@ Return values * H_UNSUPPORTED if called from the wrong context (e.g. from an SVM or before an H_SVM_INIT_START hypercall). + * H_STATE if the hypervisor could not successfully + transition the VM to Secure VM. Description ~~~~~~~~~~~
arch/powerpc/include/asm/kvm_book3s_uvmem.h +2 -0
@@ -23,6 +23,8 @@ unsigned long kvmppc_h_svm_page_out(struct kvm *kvm,unsigned long kvmppc_h_svm_init_abort (struct kvm *kvm);void kvmppc_uvmem_drop_pages (const struct kvm_memory_slot *free,struct kvm *kvm,bool skip_page_out); +int kvmppc_uv_migrate_mem_slot (struct kvm *kvm, +const struct kvm_memory_slot *memslot);#else static inline int kvmppc_uvmem_init (void ) {
arch/powerpc/kvm/book3s_hv_uvmem.c +152 -14
220 lines not on this page · raw message
Signature · 1 line
1.8.3.1
Re: [v3 3/5] KVM: PPC: Book3S HV: migrate remaining normal-GFNs to secure-GFNs in H_SVM_INIT_DONE
Quoted 170 lines · Ram Pai
The Ultravisor is expected to explicitly call
H_SVM_PAGE_INfor all the pages of the SVM before callingH_SVM_INIT_DONE. This causes a huge delay in tranistioning the VM to SVM. The Ultravisor is interested in the pages that contain the kernel, initrd and other important data structures. The rest of the pages contain throw-away content. Hence requesting just the necessary and sufficient pages from the Hypervisor is sufficient.However if not all pages are requested by the Ultravisor, the Hypervisor continues to consider the GFNs corresponding to the non-requested pages as normal GFNs. This can lead to data-corruption and undefined behavior.
Move all the PFNs associated with the SVM's GFNs to secure-PFNs, in
H_SVM_INIT_DONE. Skip the GFNs that are already Paged-in or Shared or Paged-in followed by a Paged-out.Cc Paul Mackerras <[email protected]>Cc Benjamin Herrenschmidt <[email protected]>Cc Michael Ellerman <[email protected]>Cc Bharata B Rao <[email protected]>Cc Aneesh Kumar K.V <[email protected]>Cc Sukadev Bhattiprolu <[email protected]>Cc Laurent Dufour <[email protected]>Cc Thiago Jung Bauermann <[email protected]>Cc David Gibson <[email protected]>Cc Claudio Carvalho <[email protected]>Signed-off-by Ram Pai <[email protected]>--- Documentation/powerpc/ultravisor.rst | 2 + arch/powerpc/include/asm/kvm_book3s_uvmem.h | 2 + arch/powerpc/kvm/book3s_hv_uvmem.c | 166 +++++++++++++++++++++++++--- 3 files changed, 156 insertions(+), 14 deletions(-)Documentation/powerpc/ultravisor.rst +2
-0@@ -933,6 +933,8 @@ Return values * H_UNSUPPORTED if called from the wrong context (e.g. from an SVM or before an H_SVM_INIT_START hypercall). + * H_STATE if the hypervisor could not successfully + transition the VM to Secure VM. Description ~~~~~~~~~~~arch/powerpc/include/asm/kvm_book3s_uvmem.h +2
-0@@ -23,6 +23,8 @@ unsigned long kvmppc_h_svm_page_out(struct kvm *kvm,unsigned long kvmppc_h_svm_init_abort (struct kvm *kvm);void kvmppc_uvmem_drop_pages (const struct kvm_memory_slot *free,struct kvm *kvm,bool skip_page_out); +int kvmppc_uv_migrate_mem_slot (struct kvm *kvm, +const struct kvm_memory_slot *memslot);#else static inline int kvmppc_uvmem_init (void ) {arch/powerpc/kvm/book3s_hv_uvmem.c +65
-6@@ -93,6 +93,7 @@#include <asm/ultravisor.h> #include <asm/mman.h> #include <asm/kvm_ppc.h> +#include <asm/kvm_book3s_uvmem.h> static struct dev_pagemap kvmppc_uvmem_pgmap;static unsigned long *kvmppc_uvmem_bitmap;@@ -348,6 +349,43 @@ static bool kvmppc_gfn_is_uvmem_pfn(unsigned long gfn, struct kvm *kvm,return false; } +/* +* starting from *gfn search for the next available GFN that is not yet +* transitioned to a secure GFN. return the value of that GFN in *gfn. If a +* GFN is found, return true, else return false +*/ +static bool kvmppc_next_nontransitioned_gfn (const struct kvm_memory_slot *memslot, +struct kvm *kvm,unsigned long *gfn) +{ +struct kvmppc_uvmem_slot *p; +bool ret = false; +unsigned long i; + +mutex_lock (&kvm->arch.uvmem_lock); + +list_for_each_entry (p, &kvm->arch.uvmem_pfns, list) +if (*gfn >= p->base_pfn && *gfn < p->base_pfn + p->nr_pfns) +break ; +if (!p) + goto out; +/* +* The code below assumes, one to one correspondence between +* kvmppc_uvmem_slot and memslot. +*/ +for (i = *gfn; i < p->base_pfn + p->nr_pfns; i++) { +unsigned long index = i - p->base_pfn; + +if (!(p->pfns[index] &KVMPPC_GFN_FLAG_MASK )) { + *gfn = i; + ret = true; +break ; + } + } +out: +mutex_unlock (&kvm->arch.uvmem_lock); +return ret; +} +static int kvmppc_memslot_page_merge (struct kvm *kvm,struct kvm_memory_slot *memslot,bool merge) {@@ -461,12 +499,31 @@ unsigned long kvmppc_h_svm_init_start(struct kvm *kvm)unsigned long kvmppc_h_svm_init_done (struct kvm *kvm) { +struct kvm_memslots *slots; +struct kvm_memory_slot *memslot; +int srcu_idx; +long ret =H_SUCCESS ; +if (!(kvm->arch.secure_guest &KVMPPC_SECURE_INIT_START ))return H_UNSUPPORTED ; +/* migrate any unmoved normal pfn to device pfns*/ + srcu_idx =srcu_read_lock (&kvm->srcu); + slots =kvm_memslots (kvm); +kvm_for_each_memslot (memslot, slots) { + ret =kvmppc_uv_migrate_mem_slot (kvm, memslot); +if (ret) { + ret =H_STATE ; + goto out; + } + } + kvm->arch.secure_guest |=KVMPPC_SECURE_INIT_DONE ;pr_info ("LPID %d went secure\n" , kvm->arch.lpid); -return H_SUCCESS ; + +out: +srcu_read_unlock (&kvm->srcu, srcu_idx); +return ret; }/* @@ -587,12 +644,14 @@ static struct page *kvmppc_uvmem_get_page(unsigned long gpa, struct kvm *kvm) }/* -* Alloc a PFN from private device memory pool and copy page from normal -* memory to secure memory using UV_PAGE_IN uvcall. +* Alloc a PFN from private device memory pool. If @pagein is true, +* copy page from normal memory to secure memory using UV_PAGE_IN uvcall. */ -static int kvmppc_svm_page_in (struct vm_area_struct *vma,unsigned long start, -unsigned long end,unsigned long gpa,struct kvm *kvm, -unsigned long page_shift) +static int kvmppc_svm_migrate_page (struct vm_area_struct *vma, +unsigned long start, +unsigned long end,unsigned long gpa,struct kvm *kvm, +unsigned long page_shift, +bool pagein) {unsigned long src_pfn, dst_pfn =0 ;struct migrate_vma mig;
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 675
Quoted 5 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +1
-1@@ -613,7 +672,7 @@ static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start,return ret;if (!(*mig.src &MIGRATE_PFN_MIGRATE )) { - ret =-1 ; + ret =-2 ;
migrate_vma_setup() has marked that this pfn can't be migrated. What transient errors are you observing which will disappear within 10 retries?
Also till now when UV used to pull in all the pages, we never seemed to have hit these transient errors. But now when HV is pushing the same pages, we see these errors which are disappearing after 10 retries. Can you explain this more please? What sort of pages are these?
Quoted 38 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +19
-5goto out_finalize; }@@ -623,11 +682,16 @@ static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, goto out_finalize; } - pfn = *mig.src >>MIGRATE_PFN_SHIFT ; - spage =migrate_pfn_to_page (*mig.src); -if (spage) -uv_page_in (kvm->arch.lpid, pfn << page_shift, gpa,0 , - page_shift); +if (pagein) { + pfn = *mig.src >>MIGRATE_PFN_SHIFT ; + spage =migrate_pfn_to_page (*mig.src); +if (spage) { + ret =uv_page_in (kvm->arch.lpid, pfn << page_shift, + gpa,0 , page_shift); +if (ret) + goto out_finalize; + } + } *mig.dst =migrate_pfn (page_to_pfn (dpage)) |MIGRATE_PFN_LOCKED ;migrate_vma_pages (&mig);@@ -637,6 +701,77 @@ static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, }/* +* return 1, if some page migration failed because of transient error, +* while the remaining pages migrated successfully. +* The caller can use this as a hint to retry. +* +* return 0 otherwise. *ret indicates the success status +* of this call. +*/ +static int __kvmppc_uv_migrate_mem_slot (struct kvm *kvm, +const struct kvm_memory_slot *memslot,int *ret)
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 722
Quoted 10 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +10
-0+{ +unsigned long gfn = memslot->base_gfn; +struct vm_area_struct *vma; +unsigned long start, end; +bool retry =0 ; + + *ret =0 ; +while (kvmppc_next_nontransitioned_gfn (memslot, kvm, &gfn)) { + +down_write (&kvm->mm->mmap_sem);
Acquiring and releasing mmap_sem in a loop? Any reason?
Now that you have moved ksm_madvise() calls to init time, any specific reason to take write mmap_sem here?
Quoted 13 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +13
-0+ start =gfn_to_hva (kvm, gfn); +if (kvm_is_error_hva (start)) { + *ret =H_STATE ; + goto next; + } + + end = start + (1UL <<PAGE_SHIFT ); + vma =find_vma_intersection (kvm->mm, start, end); +if (!vma || vma->vm_start > start || vma->vm_end < end) { + *ret =H_STATE ; + goto next; + } +
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 745
Quoted 10 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +10
-0+mutex_lock (&kvm->arch.uvmem_lock); + *ret =kvmppc_svm_migrate_page (vma, start, end, + (gfn <<PAGE_SHIFT ), kvm,PAGE_SHIFT , false); +mutex_unlock (&kvm->arch.uvmem_lock); + +next: +up_write (&kvm->mm->mmap_sem); + +if (*ret ==-2 ) { + retry =1 ;
Using true or false assignment makes it easy to understand the intention of this 'retry' variable.
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 752
Quoted 7 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +7
-0+continue ; + } + +if (*ret) +return 0 ; + } +return retry;
The function is supposed to return an int, but you are returning a bool.
Regards,
Bharata.
Re: [v3 3/5] KVM: PPC: Book3S HV: migrate remaining normal-GFNs to secure-GFNs in H_SVM_INIT_DONE
Quoted 11 lines · Bharata B Rao
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 675
Quoted 5 lines · Ram Pai
The Ultravisor is expected to explicitly call
H_SVM_PAGE_INfor all the pagesarch/powerpc/kvm/book3s_hv_uvmem.c +1
-1if (!(*mig.src &MIGRATE_PFN_MIGRATE )) { - ret =-1 ; + ret =-2 ;
migrate_vma_setup()has marked that this pfn can't be migrated. What transient errors are you observing which will disappear within 10 retries?
Quoted 4 lines
Also till now when UV used to pull in all the pages, we never seemed to have hit these transient errors. But now when HV is pushing the same pages, we see these errors which are disappearing after 10 retries. Can you explain this more please? What sort of pages are these?
We did see them even before this patch. The retry alleviates the problem, but does not entirely eliminate it. If the chance of seeing the issue without the patch is 1%, the chance of seeing this issue with this patch becomes 0.25%.
Quoted 4 lines
Quoted 4 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +1
-0goto out_finalize; } +bool retry =0 ;
...snip...
Quoted 10 lines
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 722
Quoted 5 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +5
-0+ + *ret =0 ; +while (kvmppc_next_nontransitioned_gfn (memslot, kvm, &gfn)) { + +down_write (&kvm->mm->mmap_sem);Acquiring and releasing
mmap_semin a loop? Any reason?Now that you have moved
ksm_madvise()calls to init time, any specific reason to take writemmap_semhere?
The semaphore protects the vma. right?
And its acquired/released in the loop, to provide the ability to relinquish the cpu without getting into a tight loop and cause softlockups.
Quoted 19 lines
Quoted 19 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +18
-0+ start =gfn_to_hva (kvm, gfn); +if (kvm_is_error_hva (start)) { + *ret =H_STATE ; + goto next; + } + + end = start + (1UL <<PAGE_SHIFT ); + vma =find_vma_intersection (kvm->mm, start, end); +if (!vma || vma->vm_start > start || vma->vm_end < end) { + *ret =H_STATE ; + goto next; + } + +mutex_lock (&kvm->arch.uvmem_lock); + *ret =kvmppc_svm_migrate_page (vma, start, end, + (gfn <<PAGE_SHIFT ), kvm,PAGE_SHIFT , false); +mutex_unlock (&kvm->arch.uvmem_lock); +
Quoted 8 lines
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 745
Quoted 5 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +5
-0+next: +up_write (&kvm->mm->mmap_sem); + +if (*ret =-2 ) { + retry =1 ;Using true or false assignment makes it easy to understand the intention of this 'retry' variable.
ok. next version will have that change.
Thanks for the comments,
RP
Re: [v3 3/5] KVM: PPC: Book3S HV: migrate remaining normal-GFNs to secure-GFNs in H_SVM_INIT_DONE
Quoted 17 lines · Ram Pai
Quoted 11 lines · Bharata B Rao
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 675
Quoted 5 lines · Ram Pai
The Ultravisor is expected to explicitly call
H_SVM_PAGE_INfor all the pagesarch/powerpc/kvm/book3s_hv_uvmem.c +1
-1if (!(*mig.src &MIGRATE_PFN_MIGRATE )) { - ret =-1 ; + ret =-2 ;
migrate_vma_setup()has marked that this pfn can't be migrated. What transient errors are you observing which will disappear within 10 retries?Quoted 4 lines
Also till now when UV used to pull in all the pages, we never seemed to have hit these transient errors. But now when HV is pushing the same pages, we see these errors which are disappearing after 10 retries. Can you explain this more please? What sort of pages are these?
Quoted 4 lines
We did see them even before this patch. The retry alleviates the problem, but does not entirely eliminate it. If the chance of seeing the issue without the patch is 1%, the chance of seeing this issue with this patch becomes 0.25%.
Okay, but may be we should investigate the problem a bit more to understand why the page migrations are failing before taking this route?
Quoted 14 lines
Quoted 5 lines
Quoted 5 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +1
-0goto out_finalize; } +bool retry =0 ;...snip...
Quoted 8 lines
arch/powerpc/kvm/book3s_hv_uvmem.c static int kvmppc_svm_page_in(struct vm_area_struct *vma, unsigned long start, · line 722
Quoted 5 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +5
-0+ + *ret =0 ; +while (kvmppc_next_nontransitioned_gfn (memslot, kvm, &gfn)) { + +down_write (&kvm->mm->mmap_sem);Acquiring and releasing
mmap_semin a loop? Any reason?
Quoted 4 lines
Quoted 2 lines
Now that you have moved
ksm_madvise()calls to init time, any specific reason to take writemmap_semhere?The semaphore protects the vma. right?
We took write lock just for ksm_madvise() and then downgraded to read. Now that you are moving that to init time, read is sufficient here.
Regards,
Bharata.
PATCH v3 4/5 KVM: PPC: Book3S HV: retry page migration before erroring-out H_SVM_PAGE_IN
In reply to Ram PaiThe page requested for page-in; sometimes, can have transient references, and hence cannot migrate immediately. Retry a few times before returning error.
H_SVM_PAGE_IN interface is enhanced to return H_BUSY if the page is not in a migratable state.
--- Documentation/powerpc/ultravisor.rst | 1 + arch/powerpc/kvm/book3s_hv_uvmem.c | 54 +++++++++++++++++++++--------------- 2 files changed, 33 insertions(+), 22 deletions(-)
Documentation/powerpc/ultravisor.rst +1 -0
@@ -1034,6 +1034,7 @@ Return values * H_PARAMETER if ``guest_pa`` is invalid. * H_P2 if ``flags`` is invalid. * H_P3 if ``order`` of page is invalid. + * H_BUSY if ``page`` is not in a state to pagein Description ~~~~~~~~~~~
arch/powerpc/kvm/book3s_hv_uvmem.c +32 -22
73 lines not on this page · raw message
Signature · 1 line
1.8.3.1
Re: [v3 4/5] KVM: PPC: Book3S HV: retry page migration before erroring-out H_SVM_PAGE_IN
Quoted 3 lines · Ram Pai
The page requested for page-in; sometimes, can have transient references, and hence cannot migrate immediately. Retry a few times before returning error.
As I noted in the previous patch, we need to understand what are these transient errors and they occur on what type of pages?
The previous patch also introduced a bit of retry logic in the page-in path. Can you consolidate the retry logic into a separate patch?
Quoted 69 lines
H_SVM_PAGE_INinterface is enhanced to returnH_BUSYif the page is not in a migratable state.Cc Paul Mackerras <[email protected]>Cc Benjamin Herrenschmidt <[email protected]>Cc Michael Ellerman <[email protected]>Cc Bharata B Rao <[email protected]>Cc Aneesh Kumar K.V <[email protected]>Cc Sukadev Bhattiprolu <[email protected]>Cc Laurent Dufour <[email protected]>Cc Thiago Jung Bauermann <[email protected]>Cc David Gibson <[email protected]>Cc Claudio Carvalho <[email protected]>Signed-off-by Ram Pai <[email protected]>--- Documentation/powerpc/ultravisor.rst | 1 + arch/powerpc/kvm/book3s_hv_uvmem.c | 54 +++++++++++++++++++++--------------- 2 files changed, 33 insertions(+), 22 deletions(-)Documentation/powerpc/ultravisor.rst +1
-0@@ -1034,6 +1034,7 @@ Return values * H_PARAMETER if ``guest_pa`` is invalid. * H_P2 if ``flags`` is invalid. * H_P3 if ``order`` of page is invalid. + * H_BUSY if ``page`` is not in a state to pagein Description ~~~~~~~~~~~arch/powerpc/kvm/book3s_hv_uvmem.c +6
-10@@ -843,7 +843,7 @@ unsigned long kvmppc_h_svm_page_in(struct kvm *kvm, unsigned long gpa,struct vm_area_struct *vma;int srcu_idx;unsigned long gfn = gpa >> page_shift; -int ret; +int ret, repeat_count =REPEAT_COUNT ;if (!(kvm->arch.secure_guest &KVMPPC_SECURE_INIT_START ))return H_UNSUPPORTED ;@@ -857,34 +857,44 @@ unsigned long kvmppc_h_svm_page_in(struct kvm *kvm, unsigned long gpa,if (flags &H_PAGE_IN_SHARED )return kvmppc_share_page (kvm, gpa, page_shift); - ret =H_PARAMETER ; srcu_idx =srcu_read_lock (&kvm->srcu); -down_write (&kvm->mm->mmap_sem); - start =gfn_to_hva (kvm, gfn); -if (kvm_is_error_hva (start)) - goto out; - -mutex_lock (&kvm->arch.uvmem_lock);/* Fail the page-in request of an already paged-in page */ -if (kvmppc_gfn_is_uvmem_pfn (gfn, kvm,NULL )) - goto out_unlock; +mutex_lock (&kvm->arch.uvmem_lock); + ret =kvmppc_gfn_is_uvmem_pfn (gfn, kvm,NULL ); +mutex_unlock (&kvm->arch.uvmem_lock); +if (ret) { +srcu_read_unlock (&kvm->srcu, srcu_idx);
arch/powerpc/kvm/book3s_hv_uvmem.c unsigned long kvmppc_h_svm_page_in(struct kvm *kvm, unsigned long gpa, · line 873
Quoted 10 lines
arch/powerpc/kvm/book3s_hv_uvmem.c +5
-4+return H_PARAMETER ; + } - end = start + (1UL << page_shift); - vma =find_vma_intersection (kvm->mm, start, end); -if (!vma || vma->vm_start > start || vma->vm_end < end) - goto out_unlock; + do { + ret = H_PARAMETER; + down_write(&kvm->mm->mmap_sem);
Again with ksm_madvise() moved to init time, check if you still need write mmap_sem here.
Regards,
Bharata.
Re: [v3 4/5] KVM: PPC: Book3S HV: retry page migration before erroring-out H_SVM_PAGE_IN
Quoted 7 lines · Bharata B Rao
Quoted 3 lines · Ram Pai
The page requested for page-in; sometimes, can have transient references, and hence cannot migrate immediately. Retry a few times before returning error.
As I noted in the previous patch, we need to understand what are these transient errors and they occur on what type of pages?
Its not clear when they occur. But they occur quite irregularly and they do occur on pages that were shared in the previous boot.
Quoted 4 lines
The previous patch also introduced a bit of retry logic in the page-in path. Can you consolidate the retry logic into a separate patch?
yes. having the retry logic in a seperate patch gives us the flexibility to drop it, if needed. The retry patch is not the core element of this patch series.
RP
PATCH v3 5/5 KVM: PPC: Book3S HV: migrate hot plugged memory
In reply to Ram PaiFrom: Laurent Dufour <[email protected]>
When a memory slot is hot plugged to a SVM, PFNs associated with the GFNs in that slot must be migrated to the secure-PFNs, aka device-PFNs.
kvmppc_uv_migrate_mem_slot() is called to accomplish this. UV_PAGE_IN ucall is skipped, since the ultravisor does not trust the content of those pages and hence ignores it.
--- arch/powerpc/kvm/book3s_hv.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
arch/powerpc/kvm/book3s_hv.c +6 -4
@@ -4523,10 +4523,12 @@ static void kvmppc_core_commit_memory_region_hv(struct kvm *kvm,case KVM_MR_CREATE :if (kvmppc_uvmem_slot_init (kvm, new))return ; -uv_register_mem_slot (kvm->arch.lpid, - new->base_gfn <<PAGE_SHIFT , - new->npages *PAGE_SIZE , -0 , new->id); +if (uv_register_mem_slot (kvm->arch.lpid, + new->base_gfn <<PAGE_SHIFT , + new->npages *PAGE_SIZE , +0 , new->id)) +return ; +kvmppc_uv_migrate_mem_slot (kvm, new);break ;case KVM_MR_DELETE :uv_unregister_mem_slot (kvm->arch.lpid, old->id);
Signature · 1 line
1.8.3.1