aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing
diff options
context:
space:
mode:
authorAneesh Kumar K.V <aneesh.kumar@linux.ibm.com>2019-09-24 09:22:53 +0530
committerMichael Ellerman <mpe@ellerman.id.au>2019-09-24 20:58:55 +1000
commit047e6575aec71d75b765c22111820c4776cd1c43 (patch)
tree8742d25f78cbcf3add79662e241546d2d7e8846c /tools/testing
parentpowerpc/book3s64/radix: Rename CPU_FTR_P9_TLBIE_BUG feature flag (diff)
downloadlinux-dev-047e6575aec71d75b765c22111820c4776cd1c43.tar.xz
linux-dev-047e6575aec71d75b765c22111820c4776cd1c43.zip
powerpc/mm: Fixup tlbie vs mtpidr/mtlpidr ordering issue on POWER9
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. Cc: stable@vger.kernel.org Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://lore.kernel.org/r/20190924035254.24612-3-aneesh.kumar@linux.ibm.com
Diffstat (limited to 'tools/testing')
0 files changed, 0 insertions, 0 deletions