A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-07 12:25:00 -04:00
Code Issues Projects Releases Packages Wiki Activity

Revert "mm: introduce CONFIG_SPECULATIVE_PAGE_FAULT"

Browse source 
This reverts commit f783633cc8.

Bug: 128240262
Change-Id: I2d5961521043932a767f828432f28e3418d7a77f
Signed-off-by: Minchan Kim <minchan@google.com>
[dereference23: Forward port to msm-5.4]
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
This commit is contained in:
Minchan Kim 2019-03-11 11:56:57 +09:00 • committed by Alexander Winkowski
commit 8a8338f6aa
No known key found for this signature in database
GPG key ID: 72762A66704CDE44
1 changed files with 0 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

23
mm/Kconfig
View file

@ -766,29 +766,6 @@ config HAVE_USERSPACE_LOW_MEMORY_KILLER
when the OOM killer and userspace memory killer both have the
potential to run).
config ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT
def_bool n
config SPECULATIVE_PAGE_FAULT
bool "Speculative page faults"
default y
depends on ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT
depends on MMU && SMP
depends on QGKI
help
Try to handle user space page faults without holding the mmap_sem.
This should allow better concurrency for massively threaded process
since the page fault handler will not wait for other threads memory
layout change to be done, assuming that this change is done in another
part of the process's memory space. This type of page fault is named
speculative page fault.
If the speculative page fault fails because of a concurrency is
detected or because underlying PMD or PTE tables are not yet
allocating, it is failing its processing and a classic page fault
is then tried.
config GUP_BENCHMARK
bool "Enable infrastructure for get_user_pages_fast() benchmarking"
help