Re: [v4 3/5] KVM: PPC: Book3S HV: in H_SVM_INIT_DONE, migrate remaining normal-GFNs to secure-GFNs.

2020-07-23 Thread Ram Pai
On Thu, Jul 23, 2020 at 11:40:37AM +0530, Bharata B Rao wrote: > On Fri, Jul 17, 2020 at 01:00:25AM -0700, Ram Pai wrote: > > > > +int kvmppc_uv_migrate_mem_slot(struct kvm *kvm, > > + const struct kvm_memory_slot *memslot) > > Don't see any callers for this outside of this file, so

Re: [v4 3/5] KVM: PPC: Book3S HV: in H_SVM_INIT_DONE, migrate remaining normal-GFNs to secure-GFNs.

2020-07-23 Thread Bharata B Rao
On Fri, Jul 17, 2020 at 01:00:25AM -0700, Ram Pai wrote: > > +int kvmppc_uv_migrate_mem_slot(struct kvm *kvm, > + const struct kvm_memory_slot *memslot) Don't see any callers for this outside of this file, so why not static? > +{ > + unsigned long gfn = memslot->base_gfn; > +

[v4 3/5] KVM: PPC: Book3S HV: in H_SVM_INIT_DONE, migrate remaining normal-GFNs to secure-GFNs.

2020-07-17 Thread Ram Pai
The 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 only interested in the pages that contain the kernel, initrd and other important data structures. The