diff options
author | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2014-04-03 13:54:59 +0200 |
---|---|---|
committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2014-04-03 14:30:55 +0200 |
commit | 02a8f3abb708919149cb657a5202f4603f0c38e2 (patch) | |
tree | 2bf430c528af833f0544f575512f7e49faf81f57 /arch/s390/kernel | |
parent | 1dad093b66fdd4fd5d7d2692169dc1bafd794628 (diff) | |
download | linux-02a8f3abb708919149cb657a5202f4603f0c38e2.tar.bz2 |
s390/mm,tlb: safeguard against speculative TLB creation
The principles of operations states that the CPU is allowed to create
TLB entries for an address space anytime while an ASCE is loaded to
the control register. This is true even if the CPU is running in the
kernel and the user address space is not (actively) accessed.
In theory this can affect two aspects of the TLB flush logic.
For full-mm flushes the ASCE of the dying process is still attached.
The approach to flush first with IDTE and then just free all page
tables can in theory lead to stale TLB entries. Use the batched
free of page tables for the full-mm flushes as well.
For operations that can have a stale ASCE in the control register,
e.g. a delayed update_user_asce in switch_mm, load the kernel ASCE
to prevent invalid TLBs from being created.
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/s390/kernel')
0 files changed, 0 insertions, 0 deletions