From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au,
linux-nvdimm@lists.01.org, dan.j.williams@intel.com
Cc: oohall@gmail.com, Jeff Moyer <jmoyer@redhat.com>,
msuchanek@suse.de, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v7 3/7] powerpc/pmem: Add flush routines using new pmem store and sync instruction
Date: Fri, 21 Jan 2022 14:37:00 +0530 [thread overview]
Message-ID: <87sftho3t7.fsf@linux.ibm.com> (raw)
In-Reply-To: <7eba6780-5ffd-54f4-feb0-b5e627ec6216@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Le 01/07/2020 à 09:22, Aneesh Kumar K.V a écrit :
>> Start using dcbstps; phwsync; sequence for flushing persistent memory range.
>> The new instructions are implemented as a variant of dcbf and hwsync and on
>> P8 and P9 they will be executed as those instructions. We avoid using them on
>> older hardware. This helps to avoid difficult to debug bugs.
>>
>
> Before this patch, the flush was done for all.
> After this patch, IIUC the flush is done only on CPUs having feature
> CPU_FTR_ARCH_207S.
>
> What about other CPUs ?
>
> I don't know much about PMEM, my concern is about the UACCESS_FLUSHCACHE
> API introduced by commit 6c44741d75a2 ("powerpc/lib: Implement
> UACCESS_FLUSHCACHE API")
>
> After your patch, __copy_from_user_flushcache() and memcpy_flushcache()
> are not doing cache flush anymore.
>
> Is that intended ?
yes, with the understanding that these functions are used with
persistent memory . We restrict the persistent memory usage to p8 and
above via commit c83040192f3763b243ece26073d61a895b4a230f
>
> I'm trying to optimise some ALSA driver that does copy_from_user +
> cache_flush for DMA, and I was wondering if using
> __copy_from_user_flushcache() was an alternative.
>
> Or is it __copy_from_user_inatomic_nocache() which has to be done for that ?
>
> Thanks
> Christophe
>
>
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
>> ---
>> arch/powerpc/include/asm/cacheflush.h | 1 +
>> arch/powerpc/lib/pmem.c | 50 ++++++++++++++++++++++++---
>> 2 files changed, 47 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/powerpc/include/asm/cacheflush.h b/arch/powerpc/include/asm/cacheflush.h
>> index de600b915a3c..54764c6e922d 100644
>> --- a/arch/powerpc/include/asm/cacheflush.h
>> +++ b/arch/powerpc/include/asm/cacheflush.h
>> @@ -6,6 +6,7 @@
>>
>> #include <linux/mm.h>
>> #include <asm/cputable.h>
>> +#include <asm/cpu_has_feature.h>
>>
>> #ifdef CONFIG_PPC_BOOK3S_64
>> /*
>> diff --git a/arch/powerpc/lib/pmem.c b/arch/powerpc/lib/pmem.c
>> index 0666a8d29596..5a61aaeb6930 100644
>> --- a/arch/powerpc/lib/pmem.c
>> +++ b/arch/powerpc/lib/pmem.c
>> @@ -9,20 +9,62 @@
>>
>> #include <asm/cacheflush.h>
>>
>> +static inline void __clean_pmem_range(unsigned long start, unsigned long stop)
>> +{
>> + unsigned long shift = l1_dcache_shift();
>> + unsigned long bytes = l1_dcache_bytes();
>> + void *addr = (void *)(start & ~(bytes - 1));
>> + unsigned long size = stop - (unsigned long)addr + (bytes - 1);
>> + unsigned long i;
>> +
>> + for (i = 0; i < size >> shift; i++, addr += bytes)
>> + asm volatile(PPC_DCBSTPS(%0, %1): :"i"(0), "r"(addr): "memory");
>> +
>> +
>> + asm volatile(PPC_PHWSYNC ::: "memory");
>> +}
>> +
>> +static inline void __flush_pmem_range(unsigned long start, unsigned long stop)
>> +{
>> + unsigned long shift = l1_dcache_shift();
>> + unsigned long bytes = l1_dcache_bytes();
>> + void *addr = (void *)(start & ~(bytes - 1));
>> + unsigned long size = stop - (unsigned long)addr + (bytes - 1);
>> + unsigned long i;
>> +
>> + for (i = 0; i < size >> shift; i++, addr += bytes)
>> + asm volatile(PPC_DCBFPS(%0, %1): :"i"(0), "r"(addr): "memory");
>> +
>> +
>> + asm volatile(PPC_PHWSYNC ::: "memory");
>> +}
>> +
>> +static inline void clean_pmem_range(unsigned long start, unsigned long stop)
>> +{
>> + if (cpu_has_feature(CPU_FTR_ARCH_207S))
>> + return __clean_pmem_range(start, stop);
>> +}
>> +
>> +static inline void flush_pmem_range(unsigned long start, unsigned long stop)
>> +{
>> + if (cpu_has_feature(CPU_FTR_ARCH_207S))
>> + return __flush_pmem_range(start, stop);
>> +}
>> +
>> /*
>> * CONFIG_ARCH_HAS_PMEM_API symbols
>> */
>> void arch_wb_cache_pmem(void *addr, size_t size)
>> {
>> unsigned long start = (unsigned long) addr;
>> - flush_dcache_range(start, start + size);
>> + clean_pmem_range(start, start + size);
>> }
>> EXPORT_SYMBOL_GPL(arch_wb_cache_pmem);
>>
>> void arch_invalidate_pmem(void *addr, size_t size)
>> {
>> unsigned long start = (unsigned long) addr;
>> - flush_dcache_range(start, start + size);
>> + flush_pmem_range(start, start + size);
>> }
>> EXPORT_SYMBOL_GPL(arch_invalidate_pmem);
>>
>> @@ -35,7 +77,7 @@ long __copy_from_user_flushcache(void *dest, const void __user *src,
>> unsigned long copied, start = (unsigned long) dest;
>>
>> copied = __copy_from_user(dest, src, size);
>> - flush_dcache_range(start, start + size);
>> + clean_pmem_range(start, start + size);
>>
>> return copied;
>> }
>> @@ -45,7 +87,7 @@ void *memcpy_flushcache(void *dest, const void *src, size_t size)
>> unsigned long start = (unsigned long) dest;
>>
>> memcpy(dest, src, size);
>> - flush_dcache_range(start, start + size);
>> + clean_pmem_range(start, start + size);
>>
>> return dest;
>> }
next prev parent reply other threads:[~2022-01-21 9:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 7:22 [PATCH v7 0/7] Support new pmem flush and sync instructions for POWER Aneesh Kumar K.V
2020-07-01 7:22 ` [PATCH v7 1/7] powerpc/pmem: Restrict papr_scm to P8 and above Aneesh Kumar K.V
2022-01-21 8:40 ` Michal Suchánek
2022-01-21 9:18 ` Aneesh Kumar K.V
2022-01-21 13:27 ` Michal Suchánek
2020-07-01 7:22 ` [PATCH v7 2/7] powerpc/pmem: Add new instructions for persistent storage and sync Aneesh Kumar K.V
2020-07-01 7:22 ` [PATCH v7 3/7] powerpc/pmem: Add flush routines using new pmem store and sync instruction Aneesh Kumar K.V
2022-01-21 7:36 ` Christophe Leroy
2022-01-21 9:07 ` Aneesh Kumar K.V [this message]
2020-07-01 7:22 ` [PATCH v7 4/7] libnvdimm/nvdimm/flush: Allow architecture to override the flush barrier Aneesh Kumar K.V
2020-07-01 7:22 ` [PATCH v7 5/7] powerpc/pmem: Update ppc64 to use the new barrier instruction Aneesh Kumar K.V
2020-07-01 7:22 ` [PATCH v7 6/7] powerpc/pmem: Avoid the barrier in flush routines Aneesh Kumar K.V
2020-07-01 7:22 ` [PATCH v7 7/7] powerpc/pmem: Initialize pmem device on newer hardware Aneesh Kumar K.V
2020-07-16 12:55 ` [PATCH v7 0/7] Support new pmem flush and sync instructions for POWER 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=87sftho3t7.fsf@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-nvdimm@lists.01.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=oohall@gmail.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).