powerpc/mm: Fixup tlbie vs store ordering issue on POWER9
Subsystems (4)
PATCH 1/6 powerpc/mm: Fixup tlbie vs store ordering issue on POWER9
From: "Aneesh Kumar K.V" <[email protected]>
commit a5d4b5891c2f1f865a2def1eb0030f534e77ff86 upstream.
On POWER9, under some circumstances, a broadcast TLB invalidation might complete before all previous stores have drained, potentially allowing stale stores from becoming visible after the invalidation. This works around it by doubling up those TLB invalidations which was verified by HW to be sufficient to close the risk window.
This will be documented in a yet-to-be-published errata.
[mpe: Enable the feature in the DT CPU features code for all Power9,
rename the feature to CPU_FTR_P9_TLBIE_BUG per benh.]
--- arch/powerpc/include/asm/cputable.h | 4 ++- arch/powerpc/kernel/dt_cpu_ftrs.c | 3 ++ arch/powerpc/kvm/book3s_64_mmu_radix.c | 3 ++ arch/powerpc/kvm/book3s_hv_rm_mmu.c | 11 +++++++ arch/powerpc/mm/hash_native_64.c | 16 +++++++++- arch/powerpc/mm/pgtable_64.c | 1 + arch/powerpc/mm/tlb-radix.c | 41 +++++++++++++++++++------- 7 files changed, 66 insertions(+), 13 deletions(-)
arch/powerpc/include/asm/cputable.h +3 -1
@@ -215,6 +215,7 @@ enum {#define CPU_FTR_DAWR LONG_ASM_CONST(0x0400000000000000)#define CPU_FTR_DABRX LONG_ASM_CONST(0x0800000000000000)#define CPU_FTR_PMAO_BUG LONG_ASM_CONST(0x1000000000000000) +#define CPU_FTR_P9_TLBIE_BUG LONG_ASM_CONST(0x2000000000000000)#define CPU_FTR_POWER9_DD1 LONG_ASM_CONST(0x4000000000000000)#ifndef __ASSEMBLY__
@@ -475,7 +476,8 @@ enum { CPU_FTR_STCX_CHECKS_ADDRESS | CPU_FTR_POPCNTB | CPU_FTR_POPCNTD | \ CPU_FTR_CFAR | CPU_FTR_HVMODE | CPU_FTR_VMX_COPY | \ CPU_FTR_DBELL | CPU_FTR_HAS_PPR | CPU_FTR_DAWR | \ - CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_ARCH_300) + CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_ARCH_300 | \ + CPU_FTR_P9_TLBIE_BUG)#define CPU_FTRS_POWER9_DD1 ((CPU_FTRS_POWER9 | CPU_FTR_POWER9_DD1) & \ (~CPU_FTR_SAO))#define CPU_FTRS_CELL (CPU_FTR_USE_TB | CPU_FTR_LWSYNC | \
arch/powerpc/kernel/dt_cpu_ftrs.c +3 -0
@@ -742,6 +742,9 @@ static __init void cpufeatures_cpu_quirks(void)*/ if ((version &0xffffff00 ) ==0x004e0100 ) cur_cpu_spec->cpu_features |=CPU_FTR_POWER9_DD1 ; + +if ((version &0xffff0000 ) ==0x004e0000 ) + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; }static void __init cpufeatures_setup_finished (void )
arch/powerpc/kvm/book3s_64_mmu_radix.c +3 -0
@@ -160,6 +160,9 @@ static void kvmppc_radix_tlbie_page(struct kvm *kvm, unsigned long addr, asmvolatile ("ptesync" : : :"memory" ); asm volatile(PPC_TLBIE_5(%0, %1, 0, 0, 1) : : "r" (addr), "r" (kvm->arch.lpid) : "memory"); +if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) + asm volatile(PPC_TLBIE_5(%0, %1, 0, 0, 1) + : : "r" (addr), "r" (kvm->arch.lpid) : "memory"); asmvolatile ("ptesync" : : :"memory" ); }
arch/powerpc/kvm/book3s_hv_rm_mmu.c +11 -0
@@ -448,6 +448,17 @@ static void do_tlbies(struct kvm *kvm, unsigned long *rbvalues, asm volatile(PPC_TLBIE_5(%0,%1,0,0,0) : : "r" (rbvalues[i]), "r" (kvm->arch.lpid)); } + +if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +/* +* Need the extra ptesync to make sure we don't +* re-order the tlbie +*/ + asmvolatile ("ptesync" : : :"memory" ); + asm volatile(PPC_TLBIE_5(%0,%1,0,0,0) : : + "r" (rbvalues[0]), "r" (kvm->arch.lpid)); + } + asmvolatile ("eieio; tlbsync; ptesync" : : :"memory" ); kvm->arch.tlbie_lock =0 ; }else {
arch/powerpc/mm/hash_native_64.c +15 -1
@@ -104,6 +104,15 @@ static inline unsigned long ___tlbie(unsigned long vpn, int psize,return va; } +static inline void fixup_tlbie (unsigned long vpn,int psize,int apsize,int ssize) +{ +if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +/* Need the extra ptesync to ensure we don't reorder tlbie*/ + asmvolatile ("ptesync" : : :"memory" ); +___tlbie (vpn, psize, apsize, ssize); + } +} +static inline void __tlbie (unsigned long vpn,int psize,int apsize,int ssize) {unsigned long rb;
@@ -181,6 +190,7 @@ static inline void tlbie(unsigned long vpn, int psize, int apsize, asmvolatile ("ptesync" : : :"memory" ); }else {__tlbie (vpn, psize, apsize, ssize); +fixup_tlbie (vpn, psize, apsize, ssize); asmvolatile ("eieio; tlbsync; ptesync" : : :"memory" ); }if (lock_tlbie && !use_local)
@@ -674,7 +684,7 @@ static void native_hpte_clear(void)*/ static void native_flush_hash_range (unsigned long number,int local) { -unsigned long vpn; +unsigned long vpn =0 ;unsigned long hash, index, hidx, shift, slot;struct hash_pte *hptep;unsigned long hpte_v;
@@ -746,6 +756,10 @@ static void native_flush_hash_range(unsigned long number, int local)__tlbie (vpn, psize, psize, ssize); }pte_iterate_hashed_end (); } +/* +* Just do one more with the last used values. +*/ +fixup_tlbie (vpn, psize, psize, ssize); asmvolatile ("eieio; tlbsync; ptesync" :::"memory" );if (lock_tlbie)
arch/powerpc/mm/pgtable_64.c +1 -0
@@ -491,6 +491,7 @@ void mmu_partition_table_set_entry(unsigned int lpid, unsigned long dw0, "r" (TLBIEL_INVAL_SET_LPID), "r" (lpid));trace_tlbie (lpid,0 ,TLBIEL_INVAL_SET_LPID , lpid,2 ,0 ,0 ); } +/* do we need fixup here ?*/ asmvolatile ("eieio; tlbsync; ptesync" : : :"memory" ); }EXPORT_SYMBOL_GPL (mmu_partition_table_set_entry);
arch/powerpc/mm/tlb-radix.c +30 -11
61 lines not on this page · raw message
Signature · 1 line
2.21.0
PATCH 2/6 powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions
From: "Aneesh Kumar K.V" <[email protected]>
commit 677733e296b5c7a37c47da391fc70a43dc40bd67 upstream.
The store ordering vs tlbie issue mentioned in commit a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9") is fixed for Nimbus 2.3 and Cumulus 1.3 revisions. We don't need to apply the fixup if we are running on them
We can only do this on PowerNV. On pseries guest with kvm we still don't support redoing the feature fixup after migration. So we should be enabling all the workarounds needed, because whe can possibly migrate between DD 2.3 and DD 2.2
--- arch/powerpc/kernel/dt_cpu_ftrs.c | 31 ++++++++++++++++++++++++++++--- 1 file changed, 28 insertions(+), 3 deletions(-)
arch/powerpc/kernel/dt_cpu_ftrs.c +28 -3
@@ -733,9 +733,35 @@ static bool __init cpufeatures_process_feature(struct dt_cpu_feature *f)return true; } +/* +* Handle POWER9 broadcast tlbie invalidation issue using +* cpu feature flag. +*/ +static __init void update_tlbie_feature_flag (unsigned long pvr) +{ +if (PVR_VER (pvr) ==PVR_POWER9 ) { +/* +* Set the tlbie feature flag for anything below +* Nimbus DD 2.3 and Cumulus DD 1.3 +*/ +if ((pvr &0xe000 ) ==0 ) { +/* Nimbus */ +if ((pvr &0xfff ) <0x203 ) + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + }else if ((pvr &0xc000 ) ==0 ) { +/* Cumulus */ +if ((pvr &0xfff ) <0x103 ) + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + }else { +WARN_ONCE (1 ,"Unknown PVR" ); + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + } + } +} +static __init void cpufeatures_cpu_quirks (void ) { -int version =mfspr (SPRN_PVR ); +unsigned long version =mfspr (SPRN_PVR );/* * Not all quirks can be derived from the cpufeatures device tree.
@@ -743,8 +769,7 @@ static __init void cpufeatures_cpu_quirks(void)if ((version &0xffffff00 ) ==0x004e0100 ) cur_cpu_spec->cpu_features |=CPU_FTR_POWER9_DD1 ; -if ((version &0xffff0000 ) ==0x004e0000 ) - cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; +update_tlbie_feature_flag (version); }static void __init cpufeatures_setup_finished (void )
Signature · 1 line
2.21.0
Patch "powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions" has been added to the 4.14-stable tree
This is a note to let you know that I've just added the patch titled
powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
powerpc-book3s64-mm-don-t-do-tlbie-fixup-for-some-hardware-revisions.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
From foo@baz Fri 08 Nov 2019 05:55:09 PM CET
From: Sandipan Das <[email protected]>
Date: Thu, 17 Oct 2019 13:35:01 +0530
Subject: powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Message-ID: <[email protected]>
From: "Aneesh Kumar K.V" <[email protected]>
commit 677733e296b5c7a37c47da391fc70a43dc40bd67 upstream.
The store ordering vs tlbie issue mentioned in commit a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9") is fixed for Nimbus 2.3 and Cumulus 1.3 revisions. We don't need to apply the fixup if we are running on them
We can only do this on PowerNV. On pseries guest with kvm we still don't support redoing the feature fixup after migration. So we should be enabling all the workarounds needed, because whe can possibly migrate between DD 2.3 and DD 2.2
--- arch/powerpc/kernel/dt_cpu_ftrs.c | 31 ++++++++++++++++++++++++++++--- 1 file changed, 28 insertions(+), 3 deletions(-)
arch/powerpc/kernel/dt_cpu_ftrs.c +28 -3
@@ -733,9 +733,35 @@ static bool __init cpufeatures_process_freturn true; } +/* +* Handle POWER9 broadcast tlbie invalidation issue using +* cpu feature flag. +*/ +static __init void update_tlbie_feature_flag (unsigned long pvr) +{ +if (PVR_VER (pvr) ==PVR_POWER9 ) { +/* +* Set the tlbie feature flag for anything below +* Nimbus DD 2.3 and Cumulus DD 1.3 +*/ +if ((pvr &0xe000 ) ==0 ) { +/* Nimbus */ +if ((pvr &0xfff ) <0x203 ) + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + }else if ((pvr &0xc000 ) ==0 ) { +/* Cumulus */ +if ((pvr &0xfff ) <0x103 ) + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + }else { +WARN_ONCE (1 ,"Unknown PVR" ); + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + } + } +} +static __init void cpufeatures_cpu_quirks (void ) { -int version =mfspr (SPRN_PVR ); +unsigned long version =mfspr (SPRN_PVR );/* * Not all quirks can be derived from the cpufeatures device tree.
@@ -743,8 +769,7 @@ static __init void cpufeatures_cpu_quirkif ((version &0xffffff00 ) ==0x004e0100 ) cur_cpu_spec->cpu_features |=CPU_FTR_POWER9_DD1 ; -if ((version &0xffff0000 ) ==0x004e0000 ) - cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; +update_tlbie_feature_flag (version); }static void __init cpufeatures_setup_finished (void )
Patches currently in stable-queue which might be from [email protected] are
queue-4.14/powerpc-book3s64-mm-don-t-do-tlbie-fixup-for-some-hardware-revisions.patch queue-4.14/selftests-powerpc-add-test-case-for-tlbie-vs-mtpidr-ordering-issue.patch queue-4.14/selftests-powerpc-fix-compile-error-on-tlbie_test-due-to-newer-gcc.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-mtpidr-mtlpidr-ordering-issue-on-power9.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-store-ordering-issue-on-power9.patch queue-4.14/powerpc-book3s64-radix-rename-cpu_ftr_p9_tlbie_bug-feature-flag.patch
PATCH 3/6 powerpc/book3s64/radix: Rename CPU_FTR_P9_TLBIE_BUG feature flag
In reply to Sandipan DasFrom: "Aneesh Kumar K.V" <[email protected]>
commit 09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0 upstream.
Rename the #define to indicate this is related to store vs tlbie ordering issue. In the next patch, we will be adding another feature flag that is used to handles ERAT flush vs tlbie ordering issue.
--- arch/powerpc/include/asm/cputable.h | 4 ++-- arch/powerpc/kernel/dt_cpu_ftrs.c | 6 +++--- arch/powerpc/kvm/book3s_64_mmu_radix.c | 2 +- arch/powerpc/kvm/book3s_hv_rm_mmu.c | 2 +- arch/powerpc/mm/hash_native_64.c | 2 +- arch/powerpc/mm/tlb-radix.c | 2 +- 6 files changed, 9 insertions(+), 9 deletions(-)
arch/powerpc/include/asm/cputable.h +2 -2
@@ -215,7 +215,7 @@ enum {#define CPU_FTR_DAWR LONG_ASM_CONST(0x0400000000000000)#define CPU_FTR_DABRX LONG_ASM_CONST(0x0800000000000000)#define CPU_FTR_PMAO_BUG LONG_ASM_CONST(0x1000000000000000) -#define CPU_FTR_P9_TLBIE_BUG LONG_ASM_CONST(0x2000000000000000) +#define CPU_FTR_P9_TLBIE_STQ_BUG LONG_ASM_CONST(0x0000400000000000)#define CPU_FTR_POWER9_DD1 LONG_ASM_CONST(0x4000000000000000)#ifndef __ASSEMBLY__
@@ -477,7 +477,7 @@ enum { CPU_FTR_CFAR | CPU_FTR_HVMODE | CPU_FTR_VMX_COPY | \ CPU_FTR_DBELL | CPU_FTR_HAS_PPR | CPU_FTR_DAWR | \ CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_ARCH_300 | \ - CPU_FTR_P9_TLBIE_BUG) + CPU_FTR_P9_TLBIE_STQ_BUG)#define CPU_FTRS_POWER9_DD1 ((CPU_FTRS_POWER9 | CPU_FTR_POWER9_DD1) & \ (~CPU_FTR_SAO))#define CPU_FTRS_CELL (CPU_FTR_USE_TB | CPU_FTR_LWSYNC | \
arch/powerpc/kernel/dt_cpu_ftrs.c +3 -3
@@ -747,14 +747,14 @@ static __init void update_tlbie_feature_flag(unsigned long pvr)if ((pvr &0xe000 ) ==0 ) {/* Nimbus */ if ((pvr &0xfff ) <0x203 ) - cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_STQ_BUG ; }else if ((pvr &0xc000 ) ==0 ) {/* Cumulus */ if ((pvr &0xfff ) <0x103 ) - cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_STQ_BUG ; }else {WARN_ONCE (1 ,"Unknown PVR" ); - cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_STQ_BUG ; } } }
arch/powerpc/kvm/book3s_64_mmu_radix.c +1 -1
@@ -160,7 +160,7 @@ static void kvmppc_radix_tlbie_page(struct kvm *kvm, unsigned long addr, asmvolatile ("ptesync" : : :"memory" ); asm volatile(PPC_TLBIE_5(%0, %1, 0, 0, 1) : : "r" (addr), "r" (kvm->arch.lpid) : "memory"); -if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) asm volatile(PPC_TLBIE_5(%0, %1, 0, 0, 1) : : "r" (addr), "r" (kvm->arch.lpid) : "memory"); asmvolatile ("ptesync" : : :"memory" );
arch/powerpc/kvm/book3s_hv_rm_mmu.c +1 -1
@@ -449,7 +449,7 @@ static void do_tlbies(struct kvm *kvm, unsigned long *rbvalues, "r" (rbvalues[i]), "r" (kvm->arch.lpid)); } -if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) {/* * Need the extra ptesync to make sure we don't * re-order the tlbie
arch/powerpc/mm/hash_native_64.c +1 -1
@@ -106,7 +106,7 @@ static inline unsigned long ___tlbie(unsigned long vpn, int psize,static inline void fixup_tlbie (unsigned long vpn,int psize,int apsize,int ssize) { -if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) {/* Need the extra ptesync to ensure we don't reorder tlbie*/ asmvolatile ("ptesync" : : :"memory" );___tlbie (vpn, psize, apsize, ssize);
arch/powerpc/mm/tlb-radix.c +1 -1
@@ -44,7 +44,7 @@ static inline void fixup_tlbie(void)unsigned long pid =0 ;unsigned long va = ((1UL <<52 ) -1 ); -if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) { asmvolatile ("ptesync" : : :"memory" );__tlbie_va (va, pid,mmu_get_ap (MMU_PAGE_64K ),RIC_FLUSH_TLB ); }
Signature · 1 line
2.21.0
Patch "powerpc/book3s64/radix: Rename CPU_FTR_P9_TLBIE_BUG feature flag" has been added to the 4.14-stable tree
This is a note to let you know that I've just added the patch titled
powerpc/book3s64/radix: Rename CPU_FTR_P9_TLBIE_BUG feature flag
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
powerpc-book3s64-radix-rename-cpu_ftr_p9_tlbie_bug-feature-flag.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
From foo@baz Fri 08 Nov 2019 05:55:09 PM CET
From: Sandipan Das <[email protected]>
Date: Thu, 17 Oct 2019 13:35:02 +0530
Subject: powerpc/book3s64/radix: Rename CPU_FTR_P9_TLBIE_BUG feature flag
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Message-ID: <[email protected]>
From: "Aneesh Kumar K.V" <[email protected]>
commit 09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0 upstream.
Rename the #define to indicate this is related to store vs tlbie ordering issue. In the next patch, we will be adding another feature flag that is used to handles ERAT flush vs tlbie ordering issue.
--- arch/powerpc/include/asm/cputable.h | 4 ++-- arch/powerpc/kernel/dt_cpu_ftrs.c | 6 +++--- arch/powerpc/kvm/book3s_64_mmu_radix.c | 2 +- arch/powerpc/kvm/book3s_hv_rm_mmu.c | 2 +- arch/powerpc/mm/hash_native_64.c | 2 +- arch/powerpc/mm/tlb-radix.c | 2 +- 6 files changed, 9 insertions(+), 9 deletions(-)
arch/powerpc/include/asm/cputable.h +2 -2
@@ -215,7 +215,7 @@ enum {#define CPU_FTR_DAWR LONG_ASM_CONST(0x0400000000000000)#define CPU_FTR_DABRX LONG_ASM_CONST(0x0800000000000000)#define CPU_FTR_PMAO_BUG LONG_ASM_CONST(0x1000000000000000) -#define CPU_FTR_P9_TLBIE_BUG LONG_ASM_CONST(0x2000000000000000) +#define CPU_FTR_P9_TLBIE_STQ_BUG LONG_ASM_CONST(0x0000400000000000)#define CPU_FTR_POWER9_DD1 LONG_ASM_CONST(0x4000000000000000)#ifndef __ASSEMBLY__
@@ -477,7 +477,7 @@ enum { CPU_FTR_CFAR | CPU_FTR_HVMODE | CPU_FTR_VMX_COPY | \ CPU_FTR_DBELL | CPU_FTR_HAS_PPR | CPU_FTR_DAWR | \ CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_ARCH_300 | \ - CPU_FTR_P9_TLBIE_BUG) + CPU_FTR_P9_TLBIE_STQ_BUG)#define CPU_FTRS_POWER9_DD1 ((CPU_FTRS_POWER9 | CPU_FTR_POWER9_DD1) & \ (~CPU_FTR_SAO))#define CPU_FTRS_CELL (CPU_FTR_USE_TB | CPU_FTR_LWSYNC | \
arch/powerpc/kernel/dt_cpu_ftrs.c +3 -3
@@ -747,14 +747,14 @@ static __init void update_tlbie_feature_if ((pvr &0xe000 ) ==0 ) {/* Nimbus */ if ((pvr &0xfff ) <0x203 ) - cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_STQ_BUG ; }else if ((pvr &0xc000 ) ==0 ) {/* Cumulus */ if ((pvr &0xfff ) <0x103 ) - cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_STQ_BUG ; }else {WARN_ONCE (1 ,"Unknown PVR" ); - cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_STQ_BUG ; } } }
arch/powerpc/kvm/book3s_64_mmu_radix.c +1 -1
@@ -160,7 +160,7 @@ static void kvmppc_radix_tlbie_page(stru asmvolatile ("ptesync" : : :"memory" ); asm volatile(PPC_TLBIE_5(%0, %1, 0, 0, 1) : : "r" (addr), "r" (kvm->arch.lpid) : "memory"); -if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) asm volatile(PPC_TLBIE_5(%0, %1, 0, 0, 1) : : "r" (addr), "r" (kvm->arch.lpid) : "memory"); asmvolatile ("ptesync" : : :"memory" );
arch/powerpc/kvm/book3s_hv_rm_mmu.c +1 -1
@@ -449,7 +449,7 @@ static void do_tlbies(struct kvm *kvm, u "r" (rbvalues[i]), "r" (kvm->arch.lpid)); } -if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) {/* * Need the extra ptesync to make sure we don't * re-order the tlbie
arch/powerpc/mm/hash_native_64.c +1 -1
@@ -106,7 +106,7 @@ static inline unsigned long ___tlbie(unstatic inline void fixup_tlbie (unsigned long vpn,int psize,int apsize,int ssize) { -if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) {/* Need the extra ptesync to ensure we don't reorder tlbie*/ asmvolatile ("ptesync" : : :"memory" );___tlbie (vpn, psize, apsize, ssize);
arch/powerpc/mm/tlb-radix.c +1 -1
@@ -44,7 +44,7 @@ static inline void fixup_tlbie(void)unsigned long pid =0 ;unsigned long va = ((1UL <<52 ) -1 ); -if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) { asmvolatile ("ptesync" : : :"memory" );__tlbie_va (va, pid,mmu_get_ap (MMU_PAGE_64K ),RIC_FLUSH_TLB ); }
Patches currently in stable-queue which might be from [email protected] are
queue-4.14/powerpc-book3s64-mm-don-t-do-tlbie-fixup-for-some-hardware-revisions.patch queue-4.14/selftests-powerpc-add-test-case-for-tlbie-vs-mtpidr-ordering-issue.patch queue-4.14/selftests-powerpc-fix-compile-error-on-tlbie_test-due-to-newer-gcc.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-mtpidr-mtlpidr-ordering-issue-on-power9.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-store-ordering-issue-on-power9.patch queue-4.14/powerpc-book3s64-radix-rename-cpu_ftr_p9_tlbie_bug-feature-flag.patch
PATCH 4/6 powerpc/mm: Fixup tlbie vs mtpidr/mtlpidr ordering issue on POWER9
In reply to Sandipan DasFrom: "Aneesh Kumar K.V" <[email protected]>
commit 047e6575aec71d75b765c22111820c4776cd1c43 upstream.
On POWER9, under some circumstances, a broadcast TLB invalidation will fail to invalidate the ERAT cache on some threads when there are parallel mtpidr/mtlpidr happening on other threads of the same core. This can cause stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie flush. This additional TLB flush will cause the ERAT cache invalidation. Since we are using PID=0 or LPID=0, we don't get filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of store vs tlbie ordering issue explained in commit:a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The presence of ERAT cache implies we can still get new stores and they may miss store queue marking flush.
--- arch/powerpc/include/asm/cputable.h | 3 +- arch/powerpc/kernel/dt_cpu_ftrs.c | 2 + arch/powerpc/kvm/book3s_hv_rm_mmu.c | 42 ++++++++++++++----- arch/powerpc/mm/hash_native_64.c | 28 +++++++++++-- arch/powerpc/mm/tlb-radix.c | 65 ++++++++++++++++++++++++----- 5 files changed, 116 insertions(+), 24 deletions(-)
arch/powerpc/include/asm/cputable.h +2 -1
@@ -217,6 +217,7 @@ enum {#define CPU_FTR_PMAO_BUG LONG_ASM_CONST(0x1000000000000000)#define CPU_FTR_P9_TLBIE_STQ_BUG LONG_ASM_CONST(0x0000400000000000)#define CPU_FTR_POWER9_DD1 LONG_ASM_CONST(0x4000000000000000) +#define CPU_FTR_P9_TLBIE_ERAT_BUG LONG_ASM_CONST(0x0001000000000000)#ifndef __ASSEMBLY__
@@ -477,7 +478,7 @@ enum { CPU_FTR_CFAR | CPU_FTR_HVMODE | CPU_FTR_VMX_COPY | \ CPU_FTR_DBELL | CPU_FTR_HAS_PPR | CPU_FTR_DAWR | \ CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_ARCH_300 | \ - CPU_FTR_P9_TLBIE_STQ_BUG) + CPU_FTR_P9_TLBIE_STQ_BUG | CPU_FTR_P9_TLBIE_ERAT_BUG)#define CPU_FTRS_POWER9_DD1 ((CPU_FTRS_POWER9 | CPU_FTR_POWER9_DD1) & \ (~CPU_FTR_SAO))#define CPU_FTRS_CELL (CPU_FTR_USE_TB | CPU_FTR_LWSYNC | \
arch/powerpc/kernel/dt_cpu_ftrs.c +2 -0
@@ -756,6 +756,8 @@ static __init void update_tlbie_feature_flag(unsigned long pvr)WARN_ONCE (1 ,"Unknown PVR" ); cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_STQ_BUG ; } + + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_ERAT_BUG ; } }
arch/powerpc/kvm/book3s_hv_rm_mmu.c +32 -10
54 lines not on this page · raw message
arch/powerpc/mm/hash_native_64.c +25 -3
@@ -104,8 +104,30 @@ static inline unsigned long ___tlbie(unsigned long vpn, int psize,return va; } -static inline void fixup_tlbie (unsigned long vpn,int psize,int apsize,int ssize) +static inline void fixup_tlbie_vpn (unsigned long vpn,int psize, +int apsize,int ssize) { +if (cpu_has_feature (CPU_FTR_P9_TLBIE_ERAT_BUG )) { +/* Radix flush for a hash guest */ + +unsigned long rb,rs,prs,r,ric; + + rb =PPC_BIT (52 );/* IS = 2 */ + rs =0 ;/* lpid = 0 */ + prs =0 ;/* partition scoped */ + r =1 ;/* radix format */ + ric =0 ;/* RIC_FLSUH_TLB */ + +/* +* Need the extra ptesync to make sure we don't +* re-order the tlbie +*/ + asmvolatile ("ptesync" : : :"memory" ); + asm volatile(PPC_TLBIE_5(%0, %4, %3, %2, %1) + : : "r"(rb), "i"(r), "i"(prs), + "i"(ric), "r"(rs) : "memory"); + } +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) {/* Need the extra ptesync to ensure we don't reorder tlbie*/ asmvolatile ("ptesync" : : :"memory" );
@@ -190,7 +212,7 @@ static inline void tlbie(unsigned long vpn, int psize, int apsize, asmvolatile ("ptesync" : : :"memory" ); }else {__tlbie (vpn, psize, apsize, ssize); -fixup_tlbie (vpn, psize, apsize, ssize); +fixup_tlbie_vpn (vpn, psize, apsize, ssize); asmvolatile ("eieio; tlbsync; ptesync" : : :"memory" ); }if (lock_tlbie && !use_local)
@@ -759,7 +781,7 @@ static void native_flush_hash_range(unsigned long number, int local)/* * Just do one more with the last used values. */ -fixup_tlbie (vpn, psize, psize, ssize); +fixup_tlbie_vpn (vpn, psize, psize, ssize); asmvolatile ("eieio; tlbsync; ptesync" :::"memory" );if (lock_tlbie)
arch/powerpc/mm/tlb-radix.c +55 -10
99 lines not on this page · raw message
Signature · 1 line
2.21.0
Patch "powerpc/mm: Fixup tlbie vs mtpidr/mtlpidr ordering issue on POWER9" has been added to the 4.14-stable tree
This is a note to let you know that I've just added the patch titled
powerpc/mm: Fixup tlbie vs mtpidr/mtlpidr ordering issue on POWER9
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
powerpc-mm-fixup-tlbie-vs-mtpidr-mtlpidr-ordering-issue-on-power9.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
From foo@baz Fri 08 Nov 2019 05:55:09 PM CET
From: Sandipan Das <[email protected]>
Date: Thu, 17 Oct 2019 13:35:03 +0530
Subject: powerpc/mm: Fixup tlbie vs mtpidr/mtlpidr ordering issue on POWER9
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Message-ID: <[email protected]>
From: "Aneesh Kumar K.V" <[email protected]>
commit 047e6575aec71d75b765c22111820c4776cd1c43 upstream.
On POWER9, under some circumstances, a broadcast TLB invalidation will fail to invalidate the ERAT cache on some threads when there are parallel mtpidr/mtlpidr happening on other threads of the same core. This can cause stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie flush. This additional TLB flush will cause the ERAT cache invalidation. Since we are using PID=0 or LPID=0, we don't get filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of store vs tlbie ordering issue explained in commit:a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The presence of ERAT cache implies we can still get new stores and they may miss store queue marking flush.
--- arch/powerpc/include/asm/cputable.h | 3 + arch/powerpc/kernel/dt_cpu_ftrs.c | 2 + arch/powerpc/kvm/book3s_hv_rm_mmu.c | 42 +++++++++++++++++------ arch/powerpc/mm/hash_native_64.c | 28 +++++++++++++-- arch/powerpc/mm/tlb-radix.c | 65 ++++++++++++++++++++++++++++++------ 5 files changed, 116 insertions(+), 24 deletions(-)
arch/powerpc/include/asm/cputable.h +2 -1
@@ -217,6 +217,7 @@ enum {#define CPU_FTR_PMAO_BUG LONG_ASM_CONST(0x1000000000000000)#define CPU_FTR_P9_TLBIE_STQ_BUG LONG_ASM_CONST(0x0000400000000000)#define CPU_FTR_POWER9_DD1 LONG_ASM_CONST(0x4000000000000000) +#define CPU_FTR_P9_TLBIE_ERAT_BUG LONG_ASM_CONST(0x0001000000000000)#ifndef __ASSEMBLY__
@@ -477,7 +478,7 @@ enum { CPU_FTR_CFAR | CPU_FTR_HVMODE | CPU_FTR_VMX_COPY | \ CPU_FTR_DBELL | CPU_FTR_HAS_PPR | CPU_FTR_DAWR | \ CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_ARCH_300 | \ - CPU_FTR_P9_TLBIE_STQ_BUG) + CPU_FTR_P9_TLBIE_STQ_BUG | CPU_FTR_P9_TLBIE_ERAT_BUG)#define CPU_FTRS_POWER9_DD1 ((CPU_FTRS_POWER9 | CPU_FTR_POWER9_DD1) & \ (~CPU_FTR_SAO))#define CPU_FTRS_CELL (CPU_FTR_USE_TB | CPU_FTR_LWSYNC | \
arch/powerpc/kernel/dt_cpu_ftrs.c +2 -0
@@ -756,6 +756,8 @@ static __init void update_tlbie_feature_WARN_ONCE (1 ,"Unknown PVR" ); cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_STQ_BUG ; } + + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_ERAT_BUG ; } }
arch/powerpc/kvm/book3s_hv_rm_mmu.c +32 -10
54 lines not on this page · raw message
arch/powerpc/mm/hash_native_64.c +25 -3
@@ -104,8 +104,30 @@ static inline unsigned long ___tlbie(unreturn va; } -static inline void fixup_tlbie (unsigned long vpn,int psize,int apsize,int ssize) +static inline void fixup_tlbie_vpn (unsigned long vpn,int psize, +int apsize,int ssize) { +if (cpu_has_feature (CPU_FTR_P9_TLBIE_ERAT_BUG )) { +/* Radix flush for a hash guest */ + +unsigned long rb,rs,prs,r,ric; + + rb =PPC_BIT (52 );/* IS = 2 */ + rs =0 ;/* lpid = 0 */ + prs =0 ;/* partition scoped */ + r =1 ;/* radix format */ + ric =0 ;/* RIC_FLSUH_TLB */ + +/* +* Need the extra ptesync to make sure we don't +* re-order the tlbie +*/ + asmvolatile ("ptesync" : : :"memory" ); + asm volatile(PPC_TLBIE_5(%0, %4, %3, %2, %1) + : : "r"(rb), "i"(r), "i"(prs), + "i"(ric), "r"(rs) : "memory"); + } +if (cpu_has_feature (CPU_FTR_P9_TLBIE_STQ_BUG )) {/* Need the extra ptesync to ensure we don't reorder tlbie*/ asmvolatile ("ptesync" : : :"memory" );
@@ -190,7 +212,7 @@ static inline void tlbie(unsigned long v asmvolatile ("ptesync" : : :"memory" ); }else {__tlbie (vpn, psize, apsize, ssize); -fixup_tlbie (vpn, psize, apsize, ssize); +fixup_tlbie_vpn (vpn, psize, apsize, ssize); asmvolatile ("eieio; tlbsync; ptesync" : : :"memory" ); }if (lock_tlbie && !use_local)
@@ -759,7 +781,7 @@ static void native_flush_hash_range(unsi/* * Just do one more with the last used values. */ -fixup_tlbie (vpn, psize, psize, ssize); +fixup_tlbie_vpn (vpn, psize, psize, ssize); asmvolatile ("eieio; tlbsync; ptesync" :::"memory" );if (lock_tlbie)
arch/powerpc/mm/tlb-radix.c +55 -10
99 lines not on this page · raw message
Patches currently in stable-queue which might be from [email protected] are
queue-4.14/powerpc-book3s64-mm-don-t-do-tlbie-fixup-for-some-hardware-revisions.patch queue-4.14/selftests-powerpc-add-test-case-for-tlbie-vs-mtpidr-ordering-issue.patch queue-4.14/selftests-powerpc-fix-compile-error-on-tlbie_test-due-to-newer-gcc.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-mtpidr-mtlpidr-ordering-issue-on-power9.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-store-ordering-issue-on-power9.patch queue-4.14/powerpc-book3s64-radix-rename-cpu_ftr_p9_tlbie_bug-feature-flag.patch
PATCH 5/6 selftests/powerpc: Add test case for tlbie vs mtpidr ordering issue
In reply to Sandipan DasFrom: "Aneesh Kumar K.V" <[email protected]>
commit 93cad5f789951eaa27c3392b15294b4e51253944 upstream.
--- tools/testing/selftests/powerpc/mm/Makefile | 2 + .../testing/selftests/powerpc/mm/tlbie_test.c | 734 ++++++++++++++++++ 2 files changed, 736 insertions(+) create mode 100644 tools/testing/selftests/powerpc/mm/tlbie_test.c
tools/testing/selftests/powerpc/mm/Makefile +2 -0
@@ -3,6 +3,7 @@ noarg: $(MAKE) -C ../ TEST_GEN_PROGS := hugetlb_vs_thp_test subpage_prot prot_sao +TEST_GEN_PROGS_EXTENDED := tlbie_test TEST_GEN_FILES := tempfile include ../../lib.mk
@@ -14,3 +15,4 @@ $(OUTPUT)/prot_sao: ../utils.c $(OUTPUT)/tempfile: dd if=/dev/zero of=$@ bs=64k count=1 +$(OUTPUT)/tlbie_test: LDLIBS += -lpthread
tools/testing/selftests/powerpc/mm/tlbie_test.c new file +734 -0
734 lines not on this page · raw message
Signature · 1 line
2.21.0
Patch "selftests/powerpc: Add test case for tlbie vs mtpidr ordering issue" has been added to the 4.14-stable tree
This is a note to let you know that I've just added the patch titled
selftests/powerpc: Add test case for tlbie vs mtpidr ordering issue
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
selftests-powerpc-add-test-case-for-tlbie-vs-mtpidr-ordering-issue.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
From foo@baz Fri 08 Nov 2019 05:55:09 PM CET
From: Sandipan Das <[email protected]>
Date: Thu, 17 Oct 2019 13:35:04 +0530
Subject: selftests/powerpc: Add test case for tlbie vs mtpidr ordering issue
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Message-ID: <[email protected]>
From: "Aneesh Kumar K.V" <[email protected]>
commit 93cad5f789951eaa27c3392b15294b4e51253944 upstream.
--- tools/testing/selftests/powerpc/mm/Makefile | 2 tools/testing/selftests/powerpc/mm/tlbie_test.c | 734 ++++++++++++++++++++++++ 2 files changed, 736 insertions(+) create mode 100644 tools/testing/selftests/powerpc/mm/tlbie_test.c
tools/testing/selftests/powerpc/mm/Makefile +2 -0
@@ -3,6 +3,7 @@ noarg: $(MAKE) -C ../ TEST_GEN_PROGS := hugetlb_vs_thp_test subpage_prot prot_sao +TEST_GEN_PROGS_EXTENDED := tlbie_test TEST_GEN_FILES := tempfile include ../../lib.mk
@@ -14,3 +15,4 @@ $(OUTPUT)/prot_sao: ../utils.c $(OUTPUT)/tempfile: dd if=/dev/zero of=$@ bs=64k count=1 +$(OUTPUT)/tlbie_test: LDLIBS += -lpthread
tools/testing/selftests/powerpc/mm/tlbie_test.c new file +734 -0
734 lines not on this page · raw message
Patches currently in stable-queue which might be from [email protected] are
queue-4.14/powerpc-book3s64-mm-don-t-do-tlbie-fixup-for-some-hardware-revisions.patch queue-4.14/selftests-powerpc-add-test-case-for-tlbie-vs-mtpidr-ordering-issue.patch queue-4.14/selftests-powerpc-fix-compile-error-on-tlbie_test-due-to-newer-gcc.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-mtpidr-mtlpidr-ordering-issue-on-power9.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-store-ordering-issue-on-power9.patch queue-4.14/powerpc-book3s64-radix-rename-cpu_ftr_p9_tlbie_bug-feature-flag.patch
PATCH 6/6 selftests/powerpc: Fix compile error on tlbie_test due to newer gcc
In reply to Sandipan DasFrom: "Desnes A. Nunes do Rosario" <[email protected]>
commit 5b216ea1c40cf06eead15054c70e238c9bd4729e upstream.
Newer versions of GCC (>= 9) demand that the size of the string to be copied must be explicitly smaller than the size of the destination. Thus, the NULL char has to be taken into account on strncpy.
This will avoid the following compiling error:
tlbie_test.c: In function 'main':
tlbie_test.c:639:4: error: 'strncpy' specified bound 100 equals destination size
strncpy(logdir, optarg, LOGDIR_NAME_SIZE);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~cc1: all warnings being treated as errors
--- tools/testing/selftests/powerpc/mm/tlbie_test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/powerpc/mm/tlbie_test.c +1 -1
@@ -636,7 +636,7 @@ int main(int argc, char *argv[]) nrthreads =strtoul (optarg,NULL ,10 );break ;case 'l' : -strncpy (logdir, optarg,LOGDIR_NAME_SIZE ); +strncpy (logdir, optarg,LOGDIR_NAME_SIZE -1 );break ;case 't' : run_time =strtoul (optarg,NULL ,10 );
Signature · 1 line
2.21.0
Patch "selftests/powerpc: Fix compile error on tlbie_test due to newer gcc" has been added to the 4.14-stable tree
This is a note to let you know that I've just added the patch titled
selftests/powerpc: Fix compile error on tlbie_test due to newer gcc
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
selftests-powerpc-fix-compile-error-on-tlbie_test-due-to-newer-gcc.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
From foo@baz Fri 08 Nov 2019 05:55:09 PM CET
From: Sandipan Das <[email protected]>
Date: Thu, 17 Oct 2019 13:35:05 +0530
Subject: selftests/powerpc: Fix compile error on tlbie_test due to newer gcc
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], "Desnes A. Nunes do Rosario" <[email protected]>
Message-ID: <[email protected]>
From: Desnes A. Nunes do Rosario <[email protected]>
commit 5b216ea1c40cf06eead15054c70e238c9bd4729e upstream.
Newer versions of GCC (>= 9) demand that the size of the string to be copied must be explicitly smaller than the size of the destination. Thus, the NULL char has to be taken into account on strncpy.
This will avoid the following compiling error:
tlbie_test.c: In function 'main':
tlbie_test.c:639:4: error: 'strncpy' specified bound 100 equals destination size
strncpy(logdir, optarg, LOGDIR_NAME_SIZE);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~cc1: all warnings being treated as errors
--- tools/testing/selftests/powerpc/mm/tlbie_test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/powerpc/mm/tlbie_test.c +1 -1
@@ -636,7 +636,7 @@ int main(int argc, char *argv[]) nrthreads =strtoul (optarg,NULL ,10 );break ;case 'l' : -strncpy (logdir, optarg,LOGDIR_NAME_SIZE ); +strncpy (logdir, optarg,LOGDIR_NAME_SIZE -1 );break ;case 't' : run_time =strtoul (optarg,NULL ,10 );
Patches currently in stable-queue which might be from [email protected] are
queue-4.14/powerpc-book3s64-mm-don-t-do-tlbie-fixup-for-some-hardware-revisions.patch queue-4.14/selftests-powerpc-add-test-case-for-tlbie-vs-mtpidr-ordering-issue.patch queue-4.14/selftests-powerpc-fix-compile-error-on-tlbie_test-due-to-newer-gcc.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-mtpidr-mtlpidr-ordering-issue-on-power9.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-store-ordering-issue-on-power9.patch queue-4.14/powerpc-book3s64-radix-rename-cpu_ftr_p9_tlbie_bug-feature-flag.patch
Patch "powerpc/mm: Fixup tlbie vs store ordering issue on POWER9" has been added to the 4.14-stable tree
In reply to Sandipan DasThis is a note to let you know that I've just added the patch titled
powerpc/mm: Fixup tlbie vs store ordering issue on POWER9
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
powerpc-mm-fixup-tlbie-vs-store-ordering-issue-on-power9.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
From foo@baz Fri 08 Nov 2019 05:55:09 PM CET
From: Sandipan Das <[email protected]>
Date: Thu, 17 Oct 2019 13:35:00 +0530
Subject: powerpc/mm: Fixup tlbie vs store ordering issue on POWER9
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], "Aneesh Kumar K.V" <[email protected]>
Message-ID: <[email protected]>
From: "Aneesh Kumar K.V" <[email protected]>
commit a5d4b5891c2f1f865a2def1eb0030f534e77ff86 upstream.
On POWER9, under some circumstances, a broadcast TLB invalidation might complete before all previous stores have drained, potentially allowing stale stores from becoming visible after the invalidation. This works around it by doubling up those TLB invalidations which was verified by HW to be sufficient to close the risk window.
This will be documented in a yet-to-be-published errata.
[mpe: Enable the feature in the DT CPU features code for all Power9,
rename the feature to CPU_FTR_P9_TLBIE_BUG per benh.]
--- arch/powerpc/include/asm/cputable.h | 4 ++- arch/powerpc/kernel/dt_cpu_ftrs.c | 3 ++ arch/powerpc/kvm/book3s_64_mmu_radix.c | 3 ++ arch/powerpc/kvm/book3s_hv_rm_mmu.c | 11 ++++++++ arch/powerpc/mm/hash_native_64.c | 16 ++++++++++++ arch/powerpc/mm/pgtable_64.c | 1 arch/powerpc/mm/tlb-radix.c | 41 ++++++++++++++++++++++++--------- 7 files changed, 66 insertions(+), 13 deletions(-)
arch/powerpc/include/asm/cputable.h +3 -1
@@ -215,6 +215,7 @@ enum {#define CPU_FTR_DAWR LONG_ASM_CONST(0x0400000000000000)#define CPU_FTR_DABRX LONG_ASM_CONST(0x0800000000000000)#define CPU_FTR_PMAO_BUG LONG_ASM_CONST(0x1000000000000000) +#define CPU_FTR_P9_TLBIE_BUG LONG_ASM_CONST(0x2000000000000000)#define CPU_FTR_POWER9_DD1 LONG_ASM_CONST(0x4000000000000000)#ifndef __ASSEMBLY__
@@ -475,7 +476,8 @@ enum { CPU_FTR_STCX_CHECKS_ADDRESS | CPU_FTR_POPCNTB | CPU_FTR_POPCNTD | \ CPU_FTR_CFAR | CPU_FTR_HVMODE | CPU_FTR_VMX_COPY | \ CPU_FTR_DBELL | CPU_FTR_HAS_PPR | CPU_FTR_DAWR | \ - CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_ARCH_300) + CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_ARCH_300 | \ + CPU_FTR_P9_TLBIE_BUG)#define CPU_FTRS_POWER9_DD1 ((CPU_FTRS_POWER9 | CPU_FTR_POWER9_DD1) & \ (~CPU_FTR_SAO))#define CPU_FTRS_CELL (CPU_FTR_USE_TB | CPU_FTR_LWSYNC | \
arch/powerpc/kernel/dt_cpu_ftrs.c +3 -0
@@ -742,6 +742,9 @@ static __init void cpufeatures_cpu_quirk*/ if ((version &0xffffff00 ) ==0x004e0100 ) cur_cpu_spec->cpu_features |=CPU_FTR_POWER9_DD1 ; + +if ((version &0xffff0000 ) ==0x004e0000 ) + cur_cpu_spec->cpu_features |=CPU_FTR_P9_TLBIE_BUG ; }static void __init cpufeatures_setup_finished (void )
arch/powerpc/kvm/book3s_64_mmu_radix.c +3 -0
@@ -160,6 +160,9 @@ static void kvmppc_radix_tlbie_page(stru asmvolatile ("ptesync" : : :"memory" ); asm volatile(PPC_TLBIE_5(%0, %1, 0, 0, 1) : : "r" (addr), "r" (kvm->arch.lpid) : "memory"); +if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) + asm volatile(PPC_TLBIE_5(%0, %1, 0, 0, 1) + : : "r" (addr), "r" (kvm->arch.lpid) : "memory"); asmvolatile ("ptesync" : : :"memory" ); }
arch/powerpc/kvm/book3s_hv_rm_mmu.c +11 -0
@@ -448,6 +448,17 @@ static void do_tlbies(struct kvm *kvm, u asm volatile(PPC_TLBIE_5(%0,%1,0,0,0) : : "r" (rbvalues[i]), "r" (kvm->arch.lpid)); } + +if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +/* +* Need the extra ptesync to make sure we don't +* re-order the tlbie +*/ + asmvolatile ("ptesync" : : :"memory" ); + asm volatile(PPC_TLBIE_5(%0,%1,0,0,0) : : + "r" (rbvalues[0]), "r" (kvm->arch.lpid)); + } + asmvolatile ("eieio; tlbsync; ptesync" : : :"memory" ); kvm->arch.tlbie_lock =0 ; }else {
arch/powerpc/mm/hash_native_64.c +15 -1
@@ -104,6 +104,15 @@ static inline unsigned long ___tlbie(unreturn va; } +static inline void fixup_tlbie (unsigned long vpn,int psize,int apsize,int ssize) +{ +if (cpu_has_feature (CPU_FTR_P9_TLBIE_BUG )) { +/* Need the extra ptesync to ensure we don't reorder tlbie*/ + asmvolatile ("ptesync" : : :"memory" ); +___tlbie (vpn, psize, apsize, ssize); + } +} +static inline void __tlbie (unsigned long vpn,int psize,int apsize,int ssize) {unsigned long rb;
@@ -181,6 +190,7 @@ static inline void tlbie(unsigned long v asmvolatile ("ptesync" : : :"memory" ); }else {__tlbie (vpn, psize, apsize, ssize); +fixup_tlbie (vpn, psize, apsize, ssize); asmvolatile ("eieio; tlbsync; ptesync" : : :"memory" ); }if (lock_tlbie && !use_local)
@@ -674,7 +684,7 @@ static void native_hpte_clear(void)*/ static void native_flush_hash_range (unsigned long number,int local) { -unsigned long vpn; +unsigned long vpn =0 ;unsigned long hash, index, hidx, shift, slot;struct hash_pte *hptep;unsigned long hpte_v;
@@ -746,6 +756,10 @@ static void native_flush_hash_range(unsi__tlbie (vpn, psize, psize, ssize); }pte_iterate_hashed_end (); } +/* +* Just do one more with the last used values. +*/ +fixup_tlbie (vpn, psize, psize, ssize); asmvolatile ("eieio; tlbsync; ptesync" :::"memory" );if (lock_tlbie)
arch/powerpc/mm/pgtable_64.c +1 -0
@@ -491,6 +491,7 @@ void mmu_partition_table_set_entry(unsig "r" (TLBIEL_INVAL_SET_LPID), "r" (lpid));trace_tlbie (lpid,0 ,TLBIEL_INVAL_SET_LPID , lpid,2 ,0 ,0 ); } +/* do we need fixup here ?*/ asmvolatile ("eieio; tlbsync; ptesync" : : :"memory" ); }EXPORT_SYMBOL_GPL (mmu_partition_table_set_entry);
arch/powerpc/mm/tlb-radix.c +30 -11
61 lines not on this page · raw message
Patches currently in stable-queue which might be from [email protected] are
queue-4.14/powerpc-book3s64-mm-don-t-do-tlbie-fixup-for-some-hardware-revisions.patch queue-4.14/selftests-powerpc-add-test-case-for-tlbie-vs-mtpidr-ordering-issue.patch queue-4.14/selftests-powerpc-fix-compile-error-on-tlbie_test-due-to-newer-gcc.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-mtpidr-mtlpidr-ordering-issue-on-power9.patch queue-4.14/powerpc-mm-fixup-tlbie-vs-store-ordering-issue-on-power9.patch queue-4.14/powerpc-book3s64-radix-rename-cpu_ftr_p9_tlbie_bug-feature-flag.patch