From: Ryan Grimm <grimm@linux.vnet.ibm.com>
To: Claudio Carvalho <cclaudio@linux.ibm.com>, linuxppc-dev@ozlabs.org
Cc: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
Michael Anderson <andmike@linux.ibm.com>,
Ram Pai <linuxram@us.ibm.com>,
kvm-ppc@vger.kernel.org, Bharata B Rao <bharata@linux.ibm.com>,
Ryan Grimm <grimm@linux.ibm.com>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Thiago Bauermann <bauerman@linux.ibm.com>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>
Subject: Re: [PATCH v4 4/8] KVM: PPC: Ultravisor: Use UV_WRITE_PATE ucall to register a PATE
Date: Wed, 17 Jul 2019 10:59:46 -0400 [thread overview]
Message-ID: <3778dbeb017d642b4f2cfe1cdce63c07209cac14.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <87ims8g24r.fsf@concordia.ellerman.id.au>
On Thu, 2019-07-11 at 22:57 +1000, Michael Ellerman wrote:
> Claudio Carvalho <cclaudio@linux.ibm.com> writes:
> > From: Michael Anderson <andmike@linux.ibm.com>
> >
> > When running under an ultravisor, the ultravisor controls the real
> > partition table and has it in secure memory where the hypervisor
> > can't
> > access it, and therefore we (the HV) have to do a ucall whenever we
> > want
> > to update an entry.
> >
> > The HV still keeps a copy of its view of the partition table in
> > normal
> > memory so that the nest MMU can access it.
> >
> > Both partition tables will have PATE entries for HV and normal
> > virtual
>
> Can you expand novel acronyms on their first usage please, ie. PATE.
>
Agreed. This confused me a while ago. It is "Partition Table Entry",
correct?
> > machines.
> >
> > Suggested-by: Ryan Grimm <grimm@linux.vnet.ibm.com>
>
Please remove this and add
Reviewed-by: Ryan Grimm <grimm@linux.ibm.com>
> "Suggested" implies this is optional, but it's not :)
>
> I'm not sure exactly what Ryan's input was, but feel free to make up
> a
> better tag :)
>
> > Signed-off-by: Michael Anderson <andmike@linux.ibm.com>
> > Signed-off-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
> > Signed-off-by: Ram Pai <linuxram@us.ibm.com>
> > [ Write the pate in HV's table before doing that in UV's ]
> > Signed-off-by: Claudio Carvalho <cclaudio@linux.ibm.com>
> > ---
> > arch/powerpc/include/asm/ultravisor-api.h | 5 +++-
> > arch/powerpc/include/asm/ultravisor.h | 14 ++++++++++
> > arch/powerpc/mm/book3s64/hash_utils.c | 3 +-
> > arch/powerpc/mm/book3s64/pgtable.c | 34
> > +++++++++++++++++++++--
> > arch/powerpc/mm/book3s64/radix_pgtable.c | 9 ++++--
> > 5 files changed, 57 insertions(+), 8 deletions(-)
> >
> > diff --git a/arch/powerpc/include/asm/ultravisor-api.h
> > b/arch/powerpc/include/asm/ultravisor-api.h
> > index 49e766adabc7..141940771add 100644
> > --- a/arch/powerpc/include/asm/ultravisor-api.h
> > +++ b/arch/powerpc/include/asm/ultravisor-api.h
> > @@ -15,6 +15,9 @@
> > #define U_SUCCESS H_SUCCESS
> > #define U_FUNCTION H_FUNCTION
> > #define U_PARAMETER H_PARAMETER
> > +#define U_PERMISSION H_PERMISSION
> >
> > -#endif /* _ASM_POWERPC_ULTRAVISOR_API_H */
>
> What happened there? Just a diff artifact?
>
> > +/* opcodes */
> > +#define UV_WRITE_PATE 0xF104
> >
> > +#endif /* _ASM_POWERPC_ULTRAVISOR_API_H */
> > diff --git a/arch/powerpc/include/asm/ultravisor.h
> > b/arch/powerpc/include/asm/ultravisor.h
> > index a78a2dacfd0b..996c1efd6c6d 100644
> > --- a/arch/powerpc/include/asm/ultravisor.h
> > +++ b/arch/powerpc/include/asm/ultravisor.h
> > @@ -12,6 +12,8 @@
> >
> > #if !defined(__ASSEMBLY__)
> >
> > +#include <linux/types.h>
> > +
> > /* Internal functions */
> > extern int early_init_dt_scan_ultravisor(unsigned long node, const
> > char *uname,
> > int depth, void *data);
> > @@ -28,8 +30,20 @@ extern int
> > early_init_dt_scan_ultravisor(unsigned long node, const char
> > *uname,
> > */
> > #if defined(CONFIG_PPC_POWERNV)
> > long ucall(unsigned long opcode, unsigned long *retbuf, ...);
> > +#else
> > +static long ucall(unsigned long opcode, unsigned long *retbuf,
> > ...)
>
> ^
> inline
>
> > +{
> > + return U_NOT_AVAILABLE;
> > +}
> > #endif
>
> That should have been in the previous patch.
>
> > +static inline int uv_register_pate(u64 lpid, u64 dw0, u64 dw1)
> > +{
> > + unsigned long retbuf[UCALL_BUFSIZE];
> > +
> > + return ucall(UV_WRITE_PATE, retbuf, lpid, dw0, dw1);
>
> You probably want a ucall_norets().
>
> > +}
> > +
> > #endif /* !__ASSEMBLY__ */
> >
> > #endif /* _ASM_POWERPC_ULTRAVISOR_H */
> > diff --git a/arch/powerpc/mm/book3s64/hash_utils.c
> > b/arch/powerpc/mm/book3s64/hash_utils.c
> > index 1ff451892d7f..220a4e133240 100644
> > --- a/arch/powerpc/mm/book3s64/hash_utils.c
> > +++ b/arch/powerpc/mm/book3s64/hash_utils.c
> > @@ -1080,9 +1080,10 @@ void hash__early_init_mmu_secondary(void)
> >
> > if (!cpu_has_feature(CPU_FTR_ARCH_300))
> > mtspr(SPRN_SDR1, _SDR1);
> > - else
> > + else if (!firmware_has_feature(FW_FEATURE_ULTRAVISOR))
> > mtspr(SPRN_PTCR,
> > __pa(partition_tb) | (PATB_SIZE_SHIFT -
> > 12));
>
> Needs a comment for the else case.
>
> > }
> > /* Initialize SLB */
> > slb_initialize();
> > diff --git a/arch/powerpc/mm/book3s64/pgtable.c
> > b/arch/powerpc/mm/book3s64/pgtable.c
> > index ad3dd977c22d..224c5c7c2e3d 100644
> > --- a/arch/powerpc/mm/book3s64/pgtable.c
> > +++ b/arch/powerpc/mm/book3s64/pgtable.c
> > @@ -16,6 +16,8 @@
> > #include <asm/tlb.h>
> > #include <asm/trace.h>
> > #include <asm/powernv.h>
> > +#include <asm/firmware.h>
> > +#include <asm/ultravisor.h>
> >
> > #include <mm/mmu_decl.h>
> > #include <trace/events/thp.h>
> > @@ -206,12 +208,25 @@ void __init mmu_partition_table_init(void)
> > * 64 K size.
> > */
> > ptcr = __pa(partition_tb) | (PATB_SIZE_SHIFT - 12);
> > - mtspr(SPRN_PTCR, ptcr);
> > + /*
> > + * If ultravisor is available, it is responsible for creating
> > and
> > + * managing partition table
> > + */
>
> But we just created the partition table?!
>
> This comment and the one below would probably make more sense if they
> were merged and appeared further up, where we allocate the partition
> table.
>
> > + if (!firmware_has_feature(FW_FEATURE_ULTRAVISOR))
> > + mtspr(SPRN_PTCR, ptcr);
> > +
> > + /*
> > + * Since nestMMU cannot access secure memory. Create
> > + * and manage our own partition table. This table
>
> But we just said the UV was responsible for it :)
>
> > + * contains entries for nonsecure and hypervisor
> > + * partition.
> > + */
> > powernv_set_nmmu_ptcr(ptcr);
> > }
> >
> > -void mmu_partition_table_set_entry(unsigned int lpid, unsigned
> > long dw0,
> > - unsigned long dw1)
> > +static void __mmu_partition_table_set_entry(unsigned int lpid,
> > + unsigned long dw0,
> > + unsigned long dw1)
> > {
> > unsigned long old = be64_to_cpu(partition_tb[lpid].patb0);
> >
> > @@ -238,6 +253,19 @@ void mmu_partition_table_set_entry(unsigned
> > int lpid, unsigned long dw0,
> > /* do we need fixup here ?*/
> > asm volatile("eieio; tlbsync; ptesync" : : : "memory");
> > }
> > +
> > +void mmu_partition_table_set_entry(unsigned int lpid, unsigned
> > long dw0,
> > + unsigned long dw1)
> > +{
> > + __mmu_partition_table_set_entry(lpid, dw0, dw1);
> > +
> > + if (firmware_has_feature(FW_FEATURE_ULTRAVISOR)) {
> > + uv_register_pate(lpid, dw0, dw1);
> > + pr_info("PATE registered by ultravisor: dw0 = 0x%lx,
> > dw1 = 0x%lx\n",
> > + dw0, dw1);
> > + }
> > +}
>
> I agree with Alexey that this patch and the next should be merged and
> the result cleaned up a bit.
>
> > +
>
> No extra blank please.
>
> > EXPORT_SYMBOL_GPL(mmu_partition_table_set_entry);
> >
> > static pmd_t *get_pmd_from_cache(struct mm_struct *mm)
> > diff --git a/arch/powerpc/mm/book3s64/radix_pgtable.c
> > b/arch/powerpc/mm/book3s64/radix_pgtable.c
> > index 8904aa1243d8..da6a6b76a040 100644
> > --- a/arch/powerpc/mm/book3s64/radix_pgtable.c
> > +++ b/arch/powerpc/mm/book3s64/radix_pgtable.c
> > @@ -656,8 +656,10 @@ void radix__early_init_mmu_secondary(void)
> > lpcr = mfspr(SPRN_LPCR);
> > mtspr(SPRN_LPCR, lpcr | LPCR_UPRT | LPCR_HR);
> >
> > - mtspr(SPRN_PTCR,
> > - __pa(partition_tb) | (PATB_SIZE_SHIFT - 12));
> > + if (!firmware_has_feature(FW_FEATURE_ULTRAVISOR))
> > + mtspr(SPRN_PTCR, __pa(partition_tb) |
> > + (PATB_SIZE_SHIFT - 12));
> > +
> > radix_init_amor();
> > }
> >
> > @@ -673,7 +675,8 @@ void radix__mmu_cleanup_all(void)
> > if (!firmware_has_feature(FW_FEATURE_LPAR)) {
> > lpcr = mfspr(SPRN_LPCR);
> > mtspr(SPRN_LPCR, lpcr & ~LPCR_UPRT);
> > - mtspr(SPRN_PTCR, 0);
> > + if (!firmware_has_feature(FW_FEATURE_ULTRAVISOR))
> > + mtspr(SPRN_PTCR, 0);
> > powernv_set_nmmu_ptcr(0);
> > radix__flush_tlb_all();
> > }
>
> There's four of these case where we skip touching the PTCR, which is
> right on the borderline of warranting an accessor. I guess we can do
> it
> as a cleanup later.
>
> cheers
>
next prev parent reply other threads:[~2019-07-17 15:02 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 20:08 [PATCH v4 0/8] kvmppc: Paravirtualize KVM to support ultravisor Claudio Carvalho
2019-06-28 20:08 ` [PATCH v4 1/8] KVM: PPC: Ultravisor: Introduce the MSR_S bit Claudio Carvalho
2019-07-08 17:38 ` janani
2019-07-11 12:57 ` Michael Ellerman
2019-07-12 0:59 ` Nicholas Piggin
2019-07-12 0:57 ` Nicholas Piggin
2019-07-12 6:29 ` Michael Ellerman
2019-07-12 21:07 ` Claudio Carvalho
2019-06-28 20:08 ` [PATCH v4 2/8] powerpc: Introduce FW_FEATURE_ULTRAVISOR Claudio Carvalho
2019-07-08 17:40 ` janani
2019-07-11 12:57 ` Michael Ellerman
2019-07-12 18:01 ` Claudio Carvalho
2019-07-15 4:10 ` Michael Ellerman
2019-06-28 20:08 ` [PATCH v4 3/8] KVM: PPC: Ultravisor: Add generic ultravisor call handler Claudio Carvalho
2019-07-08 17:55 ` janani
2019-07-11 12:57 ` Michael Ellerman
2019-07-13 17:42 ` Claudio Carvalho
2019-07-15 4:46 ` Michael Ellerman
2019-07-12 1:18 ` Nicholas Piggin
2019-06-28 20:08 ` [PATCH v4 4/8] KVM: PPC: Ultravisor: Use UV_WRITE_PATE ucall to register a PATE Claudio Carvalho
2019-07-08 17:57 ` janani
2019-07-11 12:57 ` Michael Ellerman
2019-07-17 14:59 ` Ryan Grimm [this message]
2019-07-18 21:25 ` Claudio Carvalho
2019-07-19 2:25 ` Michael Ellerman
2019-06-28 20:08 ` [PATCH v4 5/8] KVM: PPC: Ultravisor: Restrict flush of the partition tlb cache Claudio Carvalho
2019-07-01 5:54 ` Alexey Kardashevskiy
2019-07-08 20:05 ` Claudio Carvalho
2019-07-08 19:54 ` janani
2019-07-10 17:09 ` Ram Pai
2019-06-28 20:08 ` [PATCH v4 6/8] KVM: PPC: Ultravisor: Restrict LDBAR access Claudio Carvalho
2019-07-01 5:54 ` Alexey Kardashevskiy
2019-07-01 6:17 ` maddy
2019-07-01 6:30 ` Alexey Kardashevskiy
2019-07-01 6:46 ` Ram Pai
2019-07-13 17:56 ` Claudio Carvalho
2019-07-08 20:22 ` janani
2019-07-11 12:57 ` Michael Ellerman
2019-07-15 0:38 ` Claudio Carvalho
2019-06-28 20:08 ` [PATCH v4 7/8] KVM: PPC: Ultravisor: Enter a secure guest Claudio Carvalho
2019-07-08 20:53 ` janani
2019-07-08 20:52 ` Claudio Carvalho
2019-07-11 12:57 ` Michael Ellerman
2019-07-18 2:47 ` Sukadev Bhattiprolu
2019-07-22 11:05 ` Michael Ellerman
2019-07-12 2:03 ` Nicholas Piggin
2019-06-28 20:08 ` [PATCH v4 8/8] KVM: PPC: Ultravisor: Check for MSR_S during hv_reset_msr Claudio Carvalho
2019-07-08 20:54 ` janani
2019-07-11 12:57 ` Michael Ellerman
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=3778dbeb017d642b4f2cfe1cdce63c07209cac14.camel@linux.vnet.ibm.com \
--to=grimm@linux.vnet.ibm.com \
--cc=andmike@linux.ibm.com \
--cc=bauerman@linux.ibm.com \
--cc=bharata@linux.ibm.com \
--cc=cclaudio@linux.ibm.com \
--cc=grimm@linux.ibm.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=maddy@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).