diff options
author | Mateusz Guzik <mjguzik@gmail.com> | 2025-04-01 17:35:20 +0300 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2025-04-01 23:48:56 +0300 |
commit | 1701771d3069fbee154ca48e882e227fdcfbb583 (patch) | |
tree | c32762488e57a5a7f4f04b335fef8250fb55c9c9 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 2b00d9031e42eabc8d32847d231ef48b8be0373d (diff) | |
download | linux-1701771d3069fbee154ca48e882e227fdcfbb583.tar.xz |
x86/mm: Stop prefetching current->mm->mmap_lock on page faults
The prefetchw() dates back decades and the fundamental notion of doing
something like this on a lock is shady.
Moreover, for a few years now in the fast path faults are handled with RCU
+ per-vma locking, hopefully not even looking at the lock to begin with.
As such just remove it.
I did not see a point benchmarking this. Given that it is not expected
to be looked at by default justifies not doing the prefetch.
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Rik van Riel <riel@surriel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Link: https://lore.kernel.org/r/20250401143520.1113572-1-mjguzik@gmail.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions