summaryrefslogtreecommitdiff
path: root/fs/timerfd.c
diff options
context:
space:
mode:
authorHelge Deller <deller@gmx.de>2016-12-08 20:00:46 (GMT)
committerHelge Deller <deller@gmx.de>2016-12-08 20:27:18 (GMT)
commit24d0492b7d5d321a9c5846c8c974eba9823ffaa0 (patch)
treebfd151e53141d04d87b55aaffc205ed80454b440 /fs/timerfd.c
parentfebe42964fe182281859b3d43d844bb25ca49367 (diff)
downloadlinux-24d0492b7d5d321a9c5846c8c974eba9823ffaa0.tar.xz
parisc: Fix TLB related boot crash on SMP machines
At bootup we run measurements to calculate the best threshold for when we should be using full TLB flushes instead of just flushing a specific amount of TLB entries. This performance test is run over the kernel text segment. But running this TLB performance test on the kernel text segment turned out to crash some SMP machines when the kernel text pages were mapped as huge pages. To avoid those crashes this patch simply skips this test on some SMP machines and calculates an optimal threshold based on the maximum number of available TLB entries and number of online CPUs. On a technical side, this seems to happen: The TLB measurement code uses flush_tlb_kernel_range() to flush specific TLB entries with a page size of 4k (pdtlb 0(sr1,addr)). On UP systems this purge instruction seems to work without problems even if the pages were mapped as huge pages. But on SMP systems the TLB purge instruction is broadcasted to other CPUs. Those CPUs then crash the machine because the page size is not as expected. C8000 machines with PA8800/PA8900 CPUs were not affected by this problem, because the required cache coherency prohibits to use huge pages at all. Sadly I didn't found any documentation about this behaviour, so this finding is purely based on testing with phyiscal SMP machines (A500-44 and J5000, both were 2-way boxes). Cc: <stable@vger.kernel.org> # v3.18+ Signed-off-by: Helge Deller <deller@gmx.de>
Diffstat (limited to 'fs/timerfd.c')
0 files changed, 0 insertions, 0 deletions