From: Ram Pai <linuxram@us•ibm.com>
To: Laurent Dufour <ldufour@linux•ibm.com>
Cc: cclaudio@linux•ibm.com, kvm-ppc@vger•kernel.org,
bharata@linux•ibm.com, aneesh.kumar@linux•ibm.com,
sukadev@linux•vnet.ibm.com, linuxppc-dev@lists•ozlabs.org,
bauerman@linux•ibm.com, david@gibson•dropbear.id.au
Subject: Re: [PATCH v1 4/4] KVM: PPC: Book3S HV: migrate hot plugged memory
Date: Wed, 3 Jun 2020 06:25:16 -0700 [thread overview]
Message-ID: <20200603132516.GA5423@oc0525413822.ibm.com> (raw)
In-Reply-To: <1df25542-1977-fad4-c56d-b6b2c40a6852@linux.ibm.com>
On Tue, Jun 02, 2020 at 10:31:32AM +0200, Laurent Dufour wrote:
> Le 31/05/2020 à 04:27, Ram Pai a écrit :
> >From: Laurent Dufour <ldufour@linux•ibm.com>
> >
> >When a memory slot is hot plugged to a SVM, GFNs associated with that
> >memory slot automatically default to secure GFN. Hence migrate the
> >PFNs associated with these GFNs to device-PFNs.
> >
> >uv_migrate_mem_slot() is called to achieve that. It will not call
> >UV_PAGE_IN since this request is ignored by the Ultravisor.
> >NOTE: Ultravisor does not trust any page content provided by
> >the Hypervisor, ones the VM turns secure.
> >
> >Cc: Paul Mackerras <paulus@ozlabs•org>
> >Cc: Benjamin Herrenschmidt <benh@kernel•crashing.org>
> >Cc: Michael Ellerman <mpe@ellerman•id.au>
> >Cc: Bharata B Rao <bharata@linux•ibm.com>
> >Cc: Aneesh Kumar K.V <aneesh.kumar@linux•ibm.com>
> >Cc: Sukadev Bhattiprolu <sukadev@linux•vnet.ibm.com>
> >Cc: Laurent Dufour <ldufour@linux•ibm.com>
> >Cc: Thiago Jung Bauermann <bauerman@linux•ibm.com>
> >Cc: David Gibson <david@gibson•dropbear.id.au>
> >Cc: Claudio Carvalho <cclaudio@linux•ibm.com>
> >Cc: kvm-ppc@vger•kernel.org
> >Cc: linuxppc-dev@lists•ozlabs.org
> >Signed-off-by: Ram Pai <linuxram@us•ibm.com>
> > (fixed merge conflicts. Modified the commit message)
> >Signed-off-by: Laurent Dufour <ldufour@linux•ibm.com>
> >---
> > arch/powerpc/include/asm/kvm_book3s_uvmem.h | 4 ++++
> > arch/powerpc/kvm/book3s_hv.c | 11 +++++++----
> > arch/powerpc/kvm/book3s_hv_uvmem.c | 3 +--
> > 3 files changed, 12 insertions(+), 6 deletions(-)
> >
> >diff --git a/arch/powerpc/include/asm/kvm_book3s_uvmem.h b/arch/powerpc/include/asm/kvm_book3s_uvmem.h
> >index f0c5708..2ec2e5afb 100644
> >--- a/arch/powerpc/include/asm/kvm_book3s_uvmem.h
> >+++ b/arch/powerpc/include/asm/kvm_book3s_uvmem.h
> >@@ -23,6 +23,7 @@ unsigned long kvmppc_h_svm_page_out(struct kvm *kvm,
> > void kvmppc_uvmem_drop_pages(const struct kvm_memory_slot *free,
> > struct kvm *kvm, bool skip_page_out,
> > bool purge_gfn);
> >+int uv_migrate_mem_slot(struct kvm *kvm, const struct kvm_memory_slot *memslot);
> > #else
> > static inline int kvmppc_uvmem_init(void)
> > {
> >@@ -78,5 +79,8 @@ static inline int kvmppc_send_page_to_uv(struct kvm *kvm, unsigned long gfn)
> > kvmppc_uvmem_drop_pages(const struct kvm_memory_slot *free,
> > struct kvm *kvm, bool skip_page_out,
> > bool purge_gfn) { }
> >+
> >+static int uv_migrate_mem_slot(struct kvm *kvm,
> >+ const struct kvm_memory_slot *memslot);
>
> That line was not part of the patch I sent to you!
Your patch is rebased on top of my patches. This prototype declaration
is for the ifndef CONFIG_PPC_UV case.
>
>
> > #endif /* CONFIG_PPC_UV */
> > #endif /* __ASM_KVM_BOOK3S_UVMEM_H__ */
> >diff --git a/arch/powerpc/kvm/book3s_hv.c b/arch/powerpc/kvm/book3s_hv.c
> >index 4c62bfe..604d062 100644
> >--- a/arch/powerpc/kvm/book3s_hv.c
> >+++ b/arch/powerpc/kvm/book3s_hv.c
> >@@ -4516,13 +4516,16 @@ 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;
> >+ uv_migrate_mem_slot(kvm, new);
> > break;
> > case KVM_MR_DELETE:
> > uv_unregister_mem_slot(kvm->arch.lpid, old->id);
> >+ kvmppc_uvmem_drop_pages(old, kvm, true, true);
>
> Again that line has been changed from the patch I sent to you. The
> last 'true' argument has nothing to do here.
yes. i did add another parameter to kvmppc_uvmem_drop_pages() in my
patch series. So had to adapt your patch to operate on top my mine.
>
> Is that series really building?
yes. it built for me.
RP
next prev parent reply other threads:[~2020-06-03 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 2:27 [PATCH v1 0/4] Migrate non-migrated pages of a SVM Ram Pai
2020-05-31 2:27 ` [PATCH v1 1/4] KVM: PPC: Book3S HV: Fix function definition in book3s_hv_uvmem.c Ram Pai
2020-05-31 2:27 ` [PATCH v1 2/4] KVM: PPC: Book3S HV: track shared GFNs of secure VMs Ram Pai
2020-06-01 4:12 ` kbuild test robot
2020-06-05 9:48 ` Laurent Dufour
2020-06-05 14:38 ` Ram Pai
2020-05-31 2:27 ` [PATCH v1 3/4] KVM: PPC: Book3S HV: migrate remaining normal-GFNs to secure-GFNs in H_SVM_INIT_DONE Ram Pai
2020-06-01 11:55 ` Bharata B Rao
2020-06-01 19:05 ` Ram Pai
2020-06-02 10:06 ` Bharata B Rao
2020-06-03 23:10 ` Ram Pai
2020-06-04 2:31 ` Bharata B Rao
2020-05-31 2:27 ` [PATCH v1 4/4] KVM: PPC: Book3S HV: migrate hot plugged memory Ram Pai
2020-06-01 4:35 ` kbuild test robot
2020-06-01 4:45 ` kbuild test robot
2020-06-02 8:31 ` Laurent Dufour
2020-06-03 13:25 ` Ram Pai [this message]
2020-06-15 17:00 ` Laurent Dufour
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=20200603132516.GA5423@oc0525413822.ibm.com \
--to=linuxram@us$(echo .)ibm.com \
--cc=aneesh.kumar@linux$(echo .)ibm.com \
--cc=bauerman@linux$(echo .)ibm.com \
--cc=bharata@linux$(echo .)ibm.com \
--cc=cclaudio@linux$(echo .)ibm.com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=kvm-ppc@vger$(echo .)kernel.org \
--cc=ldufour@linux$(echo .)ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sukadev@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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