lmkd: Select in-kernel vs userspace lmk based on kernel driver presence
(cherry pick from commit 979591b627)
Currently selection criteria for in-kernel vs userspace lmk is kernel
driver presence and device not being a Go device. This change removes
Go device check leaving kernel driver presence to be the only selection
criteria.
Bug: 71502948
Change-Id: I394a7920433a8d090e207ea86296356413a63fe7
Merged-In: I394a7920433a8d090e207ea86296356413a63fe7
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
This commit is contained in:
parent
63dadcf79e
commit
2088f6ad03
1 changed files with 1 additions and 1 deletions
|
|
@ -1038,7 +1038,7 @@ static int init(void) {
|
|||
maxevents++;
|
||||
|
||||
has_inkernel_module = !access(INKERNEL_MINFREE_PATH, W_OK);
|
||||
use_inkernel_interface = has_inkernel_module && !is_go_device;
|
||||
use_inkernel_interface = has_inkernel_module;
|
||||
|
||||
if (use_inkernel_interface) {
|
||||
ALOGI("Using in-kernel low memory killer interface");
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue