Merge Initial Changes into rad-hmp from android-q-eas #14

radcolor · 2019-12-10T17:44:57Z

We were going to do eas implementation on android-q-eas, so merge all initial changes in this branch.

Give fingerprintd the highest priority (MIN_NICE) when the screen is off to speed up fingerprint processing, and then reset its priority back to normal when the screen is on. Signed-off-by: Sultanxda <[email protected]> There are now 2 fingerprint related processes: - [email protected] -> comm:[email protected] - com.qualcomm.qti.biometrics.fingerprint.service -> comm:erprint.service For the match to work properly, use strstr() with "erprint". Signed-off-by: Park Ju Hyung <[email protected]>

@0ctobot

sysfs groups should only be readable and writable, not executable Signed-off-by: Francisco Franco <[email protected]> [@0ctobot: Fix invalid permissions] Signed-off-by: Adam W. Willis <[email protected]>

Signed-off-by: andip71 <[email protected]> Signed-off-by: djb77 <[email protected]> Signed-off-by: meg4z0rd <[email protected]>

The purpose of Anxiety is to improve throughput on latency-sensitive tasks on embedded flash storage devices. On modern devices, embedded systems contain relatively fast storage, so spending too much time with complicated queue-shifting scheduling algorithms may end up bottlenecking the device. Similarly to the No-op I/O scheduler, Anxiety works with a FIFO queue; however, Anxiety includes basic request logic based on READ v. WRITE requests. WRITE requests are starved at a fixed ratio, defined as the `max_writes_starved` tunable. READ requests are given priority over WRITE requests due to their essentiality in determining load-time latency. ------------------TEST-------------------- SCHEDULERS Anxiety CFQ S. READ 286.22 280.74 S. WRITE 221.01 174.0 R. READ 41.35 47.89 R. WRITE 10.65 10.7 SQL INS. 1276.57 1121.25 SQL UPD. 2920.97 2978.74 SQL DEL. 2503.16 2642.3 ------------------------------------------ Tests were done using AndroBench on a Xiaomi Mi A2 on the latest 4.4.178 patch. This application has been known to be misrepresentative on I/O scores in the past. Signed-off-by: Tyler Nijmeh <[email protected]>

Some requests would like to be treated as a synchronous request. In this case, we can allow these special requests to be part of the READ FIFO list. They are treated as READ requests, inheriting their request biases. Also, READ requests are always treated as sync. Signed-off-by: Tyler Nijmeh <[email protected]>

This results in far faster application start speeds. Signed-off-by: Tyler Nijmeh <[email protected]>

Squashed with "block: maple: Convert to State Notifier" Signed-off-by: Joe Maples <[email protected]> Signed-off-by: Nathan Chancellor <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

Used checkpatch.pl; the 80 line length warnings were left alone. Signed-off-by: Nathan Chancellor <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

@GUYVER91

credits to @GUYVER91

The use of symbolic permissions is deprecated and discouraged Change-Id: I440ba7ca32eae85f07795c2ec8177259e9faa9c7 Signed-off-by: Harsh Shandilya <[email protected]>

@nathanchance

[@nathanchance: Fix checkpatch.pl warnings] Signed-off-by: Nathan Chancellor <[email protected]> Change-Id: Iad4128b72ccecd36b0aae0d51075018a47c2affb

Signed-off-by: flar2 <[email protected]>

@robcore

credits to @robcore Signed-off-by: ktommy91 <[email protected]>

Based on ideas of FranciscoFranco's non-generic driver. Sysfs node: /sys/class/misc/boeffla_wakelock_blocker/wakelock_blocker - list of wakelocks to be blocked, separated by semicolons /sys/class/misc/boeffla_wakelock_blocker/debug - write: 0/1 to switch off and on debug logging into dmesg - read: get current driver internals /sys/class/misc/boeffla_wakelock_blocker/version - show driver version Signed-off-by: andip71 <[email protected]> Conflicts: kernel/power/Kconfig

- currently active wakelocks on the list are forcefully killed

There are now two lists: - the previously existing list of user defined wakelocks to block - a new list called "wakelock_blocker_default" which comes prepopulated with the most common and safe wakelocks to block: qcom_rx_wakelock;wlan;wlan_wow_wl;wlan_extscan_wl;netmgr_wl;NETLINK A combination of both wakelock lists will be blocked finally.

sensor_ind;[timerfd]

Signed-off-by: Francisco Franco <[email protected]> Signed-off-by: Mihran Thalhath <[email protected]> Conflicts: drivers/base/power/boeffla_wl_blocker.h

Signed-off-by: Francisco Franco <[email protected]> Conflicts: drivers/base/power/boeffla_wl_blocker.h

Signed-off-by: rad <[email protected]>

@savoca

Adding the kcal interface by @savoca and @faux123 porting from m9 version by @flar2 Using the MDP 1_7 userspace structs to inject configurations of kcal to the pp_cache configs. Overriding userspace copy with memcpy when copy_from_user fails (in case of kcal interface used). Adding a simple mdp ctl struct caching to the kcal driver to grab ctl struct for config calls. Could be done nicer with direct interfacing to userspace, leaves some space to make the kernel crash if a third party app sends faulty configs, but there's no security issue or degradation of functionality with this memcpy patch. @tbalden

Android uses a 1 MiB console ramoops region, which requires kmalloc to be changed to vmalloc in the following places: 1. pstore_mkfile(), allocation of inode->i_private 2. ramoops_pstore_read(), allocation of buf Bug: 67383905 Change-Id: Ie4f355a5991b7cb6ad356ded7bd9d41630602bf5 Signed-off-by: Siqi Lin <[email protected]>

Userspace reads /proc/config.gz and spits out an error message after boot finishes when it doesn't like the kernel's configuration. In order to preserve our freedom to customize the kernel however we'd like, show userspace the stock xiaomi config so that it never complains about our kernel configuration. Signed-off-by: Sultan Alsawaf <[email protected]> Signed-off-by: Subhajeet Muhuri <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

Userspace parses this and sets the ro.boot.verifiedbootstate prop according to the value that this flag has. When ro.boot.verifiedbootstate is not 'green', SafetyNet is tripped and fails the CTS test. Hide verifiedbootstate from /proc/cmdline in order to fix the failed SafetyNet CTS check. Signed-off-by: Sultanxda <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

SafetyNet checks androidboot.veritymode in Nougat, so remove it. Additionally, remove androidboot.enable_dm_verity and androidboot.secboot in case SafetyNet will check them in the future. Signed-off-by: Sultanxda <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

Signed-off-by: srfarias <[email protected]>

Signed-off-by: rad <[email protected]>

based on this commit: 41ee0ba7f37a4505f91190644375e86eca92b0e1 Change-Id: Ieb57814024d8b6f2108ed3c84d6c6d3a7682ac42

Ashmem uses a single big mutex lock for all synchronization, and even uses it when no synchronization issues are present. The contention from using a single lock results in all-around poor performance. Use fine-grained locks and atomic constructions to eliminate the big mutex lock, thereby improving performance greatly. Signed-off-by: Sultan Alsawaf <[email protected]>

Fuelgauge is relatively unimportant in the wide spectrum of kernel drivers. Fuelgauge uses far too many wakelocks than are necessary. Signed-off-by: Tyler Nijmeh <[email protected]>

qcom_rx_wakelock is one of the major culprit to increased power consumption. Although its total wakelock time is quite low, it's catched very frequently and prevents the system from entering suspend repeatedly. Original intention of this wakelock is to prevent dropping unicast or local ARP packet, but I'm having a hard time understanding why are those packets critical to regular Android users. qcacld's packet filter will still allow notifications to flow in. Disable qcom_rx_wakelock by forcing rx_wakelock_timeout to 0. Signed-off-by: Park Ju Hyung <[email protected]> Signed-off-by: kdrag0n <[email protected]>

Signed-off-by: srfarias <[email protected]>

Change-Id: I62f5de46e4d1cf4a911d3c487cfa7429177a6ff7

@nathanchance

[@nathanchance: Change permissions to 0644 to avoid runtime warning] Signed-off-by: Nathan Chancellor <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

@nathanchance

Intention is mainly to limit the minimum brightness for the lcd backlight as OP5 auto brightness handling seems a bit too aggressive when it gets dark. [@nathanchance: Adjust permissions and remove max limit] Signed-off-by: Nathan Chancellor <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

Signed-off-by: Mihran Thalhath <[email protected]>

echo 0 /sys/kernel/fast_charge/force_fast_charge (disable) echo 1 /sys/kernel/fast_charge/force_fast_charge (enable) Enables force charging up to 900mA in usb mode Signed-off-by: engstk <[email protected]> Signed-off-by: Tyler Nijmeh <[email protected]>

radcolor

Reviewing all changes

radcolor

Reviewing all changes done.

This patch is to fix a crash: #3 [ffffb6580689f898] oops_end at ffffffffa2835bc2 #4 [ffffb6580689f8b8] no_context at ffffffffa28766e7 #5 [ffffb6580689f920] async_page_fault at ffffffffa320135e [exception RIP: f2fs_is_compressed_page+34] RIP: ffffffffa2ba83a2 RSP: ffffb6580689f9d8 RFLAGS: 00010213 RAX: 0000000000000001 RBX: fffffc0f50b34bc0 RCX: 0000000000002122 RDX: 0000000000002123 RSI: 0000000000000c00 RDI: fffffc0f50b34bc0 RBP: ffff97e815a40178 R8: 0000000000000000 R9: ffff97e83ffc9000 R10: 0000000000032300 R11: 0000000000032380 R12: ffffb6580689fa38 R13: fffffc0f50b34bc0 R14: ffff97e825cbd000 R15: 0000000000000c00 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #6 [ffffb6580689f9d8] __is_cp_guaranteed at ffffffffa2b7ea98 #7 [ffffb6580689f9f0] f2fs_submit_page_write at ffffffffa2b81a69 #8 [ffffb6580689fa30] f2fs_do_write_meta_page at ffffffffa2b99777 #9 [ffffb6580689fae0] __f2fs_write_meta_page at ffffffffa2b75f1a #10 [ffffb6580689fb18] f2fs_sync_meta_pages at ffffffffa2b77466 #11 [ffffb6580689fc98] do_checkpoint at ffffffffa2b78e46 #12 [ffffb6580689fd88] f2fs_write_checkpoint at ffffffffa2b79c29 #13 [ffffb6580689fdd0] f2fs_sync_fs at ffffffffa2b69d95 #14 [ffffb6580689fe20] sync_filesystem at ffffffffa2ad2574 #15 [ffffb6580689fe30] generic_shutdown_super at ffffffffa2a9b582 #16 [ffffb6580689fe48] kill_block_super at ffffffffa2a9b6d1 #17 [ffffb6580689fe60] kill_f2fs_super at ffffffffa2b6abe1 #18 [ffffb6580689fea0] deactivate_locked_super at ffffffffa2a9afb6 #19 [ffffb6580689feb8] cleanup_mnt at ffffffffa2abcad4 #20 [ffffb6580689fee0] task_work_run at ffffffffa28bca28 #21 [ffffb6580689ff00] exit_to_usermode_loop at ffffffffa28050b7 #22 [ffffb6580689ff38] do_syscall_64 at ffffffffa280560e #23 [ffffb6580689ff50] entry_SYSCALL_64_after_hwframe at ffffffffa320008c This occurred when umount f2fs if enable F2FS_FS_COMPRESSION with F2FS_IO_TRACE. Fixes it by adding IS_IO_TRACED_PAGE to check validity of pid for page_private. Signed-off-by: Yu Changchun <[email protected]> Reviewed-by: Chao Yu <[email protected]> Signed-off-by: Jaegeuk Kim <[email protected]>

[ Upstream commit e24c6447ccb7b1a01f9bf0aec94939e6450c0b4d ] I compiled with AddressSanitizer and I had these memory leaks while I was using the tep_parse_format function: Direct leak of 28 byte(s) in 4 object(s) allocated from: #0 0x7fb07db49ffe in __interceptor_realloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dffe) #1 0x7fb07a724228 in extend_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:985 #2 0x7fb07a724c21 in __read_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1140 #3 0x7fb07a724f78 in read_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1206 #4 0x7fb07a725191 in __read_expect_type /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1291 #5 0x7fb07a7251df in read_expect_type /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1299 #6 0x7fb07a72e6c8 in process_dynamic_array_len /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:2849 #7 0x7fb07a7304b8 in process_function /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3161 #8 0x7fb07a730900 in process_arg_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3207 #9 0x7fb07a727c0b in process_arg /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1786 #10 0x7fb07a731080 in event_read_print_args /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3285 #11 0x7fb07a731722 in event_read_print /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3369 #12 0x7fb07a740054 in __tep_parse_format /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6335 #13 0x7fb07a74047a in __parse_event /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6389 #14 0x7fb07a740536 in tep_parse_format /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6431 #15 0x7fb07a785acf in parse_event ../../../src/fs-src/fs.c:251 #16 0x7fb07a785ccd in parse_systems ../../../src/fs-src/fs.c:284 #17 0x7fb07a786fb3 in read_metadata ../../../src/fs-src/fs.c:593 #18 0x7fb07a78760e in ftrace_fs_source_init ../../../src/fs-src/fs.c:727 #19 0x7fb07d90c19c in add_component_with_init_method_data ../../../../src/lib/graph/graph.c:1048 #20 0x7fb07d90c87b in add_source_component_with_initialize_method_data ../../../../src/lib/graph/graph.c:1127 #21 0x7fb07d90c92a in bt_graph_add_source_component ../../../../src/lib/graph/graph.c:1152 #22 0x55db11aa632e in cmd_run_ctx_create_components_from_config_components ../../../src/cli/babeltrace2.c:2252 #23 0x55db11aa6fda in cmd_run_ctx_create_components ../../../src/cli/babeltrace2.c:2347 #24 0x55db11aa780c in cmd_run ../../../src/cli/babeltrace2.c:2461 #25 0x55db11aa8a7d in main ../../../src/cli/babeltrace2.c:2673 #26 0x7fb07d5460b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2) The token variable in the process_dynamic_array_len function is allocated in the read_expect_type function, but is not freed before calling the read_token function. Free the token variable before calling read_token in order to plug the leak. Signed-off-by: Philippe Duplessis-Guindon <[email protected]> Reviewed-by: Steven Rostedt (VMware) <[email protected]> Link: https://lore.kernel.org/linux-trace-devel/[email protected] Signed-off-by: Arnaldo Carvalho de Melo <[email protected]> Signed-off-by: Sasha Levin <[email protected]>

This patch is to fix a crash: #3 [ffffb6580689f898] oops_end at ffffffffa2835bc2 #4 [ffffb6580689f8b8] no_context at ffffffffa28766e7 #5 [ffffb6580689f920] async_page_fault at ffffffffa320135e [exception RIP: f2fs_is_compressed_page+34] RIP: ffffffffa2ba83a2 RSP: ffffb6580689f9d8 RFLAGS: 00010213 RAX: 0000000000000001 RBX: fffffc0f50b34bc0 RCX: 0000000000002122 RDX: 0000000000002123 RSI: 0000000000000c00 RDI: fffffc0f50b34bc0 RBP: ffff97e815a40178 R8: 0000000000000000 R9: ffff97e83ffc9000 R10: 0000000000032300 R11: 0000000000032380 R12: ffffb6580689fa38 R13: fffffc0f50b34bc0 R14: ffff97e825cbd000 R15: 0000000000000c00 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #6 [ffffb6580689f9d8] __is_cp_guaranteed at ffffffffa2b7ea98 #7 [ffffb6580689f9f0] f2fs_submit_page_write at ffffffffa2b81a69 #8 [ffffb6580689fa30] f2fs_do_write_meta_page at ffffffffa2b99777 #9 [ffffb6580689fae0] __f2fs_write_meta_page at ffffffffa2b75f1a #10 [ffffb6580689fb18] f2fs_sync_meta_pages at ffffffffa2b77466 #11 [ffffb6580689fc98] do_checkpoint at ffffffffa2b78e46 #12 [ffffb6580689fd88] f2fs_write_checkpoint at ffffffffa2b79c29 #13 [ffffb6580689fdd0] f2fs_sync_fs at ffffffffa2b69d95 #14 [ffffb6580689fe20] sync_filesystem at ffffffffa2ad2574 #15 [ffffb6580689fe30] generic_shutdown_super at ffffffffa2a9b582 #16 [ffffb6580689fe48] kill_block_super at ffffffffa2a9b6d1 #17 [ffffb6580689fe60] kill_f2fs_super at ffffffffa2b6abe1 #18 [ffffb6580689fea0] deactivate_locked_super at ffffffffa2a9afb6 #19 [ffffb6580689feb8] cleanup_mnt at ffffffffa2abcad4 #20 [ffffb6580689fee0] task_work_run at ffffffffa28bca28 #21 [ffffb6580689ff00] exit_to_usermode_loop at ffffffffa28050b7 #22 [ffffb6580689ff38] do_syscall_64 at ffffffffa280560e #23 [ffffb6580689ff50] entry_SYSCALL_64_after_hwframe at ffffffffa320008c This occurred when umount f2fs if enable F2FS_FS_COMPRESSION with F2FS_IO_TRACE. Fixes it by adding IS_IO_TRACED_PAGE to check validity of pid for page_private. Signed-off-by: Yu Changchun <[email protected]> Reviewed-by: Chao Yu <[email protected]> Signed-off-by: Jaegeuk Kim <[email protected]>

kerneltoast and others added 30 commits December 10, 2019 19:22

Added fsync on/off support.

0b3da81

sysfs groups should only be readable and writable, not executable Signed-off-by: Francisco Franco <[email protected]> [@0ctobot: Fix invalid permissions] Signed-off-by: Adam W. Willis <[email protected]>

block: Add ZEN v2 scheduler

42538b7

Signed-off-by: andip71 <[email protected]> Signed-off-by: djb77 <[email protected]> Signed-off-by: meg4z0rd <[email protected]>

block: anxiety: Increase write starvation limit

2f77bcd

This results in far faster application start speeds. Signed-off-by: Tyler Nijmeh <[email protected]>

block: Add Maple I/O Scheduler

e1f1f07

Squashed with "block: maple: Convert to State Notifier" Signed-off-by: Joe Maples <[email protected]> Signed-off-by: Nathan Chancellor <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

block: maple: Improve coding style

a5243e1

Used checkpatch.pl; the 80 line length warnings were left alone. Signed-off-by: Nathan Chancellor <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

block: tweak maple

e733108

credits to @GUYVER91

block: maple-iosched: Use octal permissions

671e713

The use of symbolic permissions is deprecated and discouraged Change-Id: I440ba7ca32eae85f07795c2ec8177259e9faa9c7 Signed-off-by: Harsh Shandilya <[email protected]>

block: maple-iosched: Convert to use fb_notifier

30238b1

[@nathanchance: Fix checkpatch.pl warnings] Signed-off-by: Nathan Chancellor <[email protected]> Change-Id: Iad4128b72ccecd36b0aae0d51075018a47c2affb

Add SIO and FIOPS i/o schedulers

cc75d97

Signed-off-by: flar2 <[email protected]>

FIOPS: update for linux 3.18

4f3cd75

SIO: update for linux 3.18

6f4f1eb

block: modify fiops

fecfb0b

credits to @robcore Signed-off-by: ktommy91 <[email protected]>

boeffla_wl_blocker: update to wakelock blocker driver v1.0.1

7f84372

- currently active wakelocks on the list are forcefully killed

boeffla_wl_blocker: Increase length_list & add more defaults

90fd45b

sensor_ind;[timerfd]

wl_blocker: add more wakelocks to the default block list

8f9046c

Signed-off-by: Francisco Franco <[email protected]> Signed-off-by: Mihran Thalhath <[email protected]> Conflicts: drivers/base/power/boeffla_wl_blocker.h

power: block two more wakelocks just in case

bdb6613

Signed-off-by: Francisco Franco <[email protected]> Conflicts: drivers/base/power/boeffla_wl_blocker.h

whyred: defconfig: enable boeffla wakelock blocker driver

eba7113

Signed-off-by: rad <[email protected]>

msm: mdss: KCAL: disable igc update

09d0429

Whyred: defconfig: enable kcal

e672a06

scripts: remove localversion "+" from kernel version strings

aa97ade

ericfrs and others added 15 commits December 10, 2019 20:50

whyred-perf_defconfig: enable ntfs support

f20845b

Signed-off-by: srfarias <[email protected]>

whyred-perf_defconfig: drop sdm630

0d7315e

Signed-off-by: srfarias <[email protected]>

dts: sdm660: remove dm verity

70a408f

Signed-off-by: rad <[email protected]>

ARM: dts: msm: add the missing sRGB on/off commands for some panels

2a82b2b

tianma: td4310: add missing srgb and ce on/off commands

b416ff1

Signed-off-by: rad <[email protected]>

whyred/tulip: update GPU ID to use Adreno 512

452bc5b

based on this commit: 41ee0ba7f37a4505f91190644375e86eca92b0e1 Change-Id: Ieb57814024d8b6f2108ed3c84d6c6d3a7682ac42

power: qpnp-fg: Don't hold wakelocks

7ebd832

Fuelgauge is relatively unimportant in the wide spectrum of kernel drivers. Fuelgauge uses far too many wakelocks than are necessary. Signed-off-by: Tyler Nijmeh <[email protected]>

dts: qcom: whyred/tulip/wayne: fix boot on oreo fw

1d1aead

Signed-off-by: srfarias <[email protected]>

qpnp-haptic: make its strength adjustable via VibratorHW

fc6a068

Change-Id: I62f5de46e4d1cf4a911d3c487cfa7429177a6ff7

mdss_fb: add backlight dimmer option

4acb3ec

[@nathanchance: Change permissions to 0644 to avoid runtime warning] Signed-off-by: Nathan Chancellor <[email protected]> Signed-off-by: Akhil Narang <[email protected]>

sound: sdm660_cdc: Correct the limits

6b527ad

Signed-off-by: Mihran Thalhath <[email protected]>

radcolor commented Dec 10, 2019

View reviewed changes

radcolor merged commit 51b4827 into rad-hmp Dec 10, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Merge Initial Changes into rad-hmp from android-q-eas #14

Merge Initial Changes into rad-hmp from android-q-eas #14

radcolor commented Dec 10, 2019

radcolor left a comment

radcolor left a comment

Merge Initial Changes into rad-hmp from android-q-eas #14

Merge Initial Changes into rad-hmp from android-q-eas #14

Conversation

radcolor commented Dec 10, 2019

radcolor left a comment

Choose a reason for hiding this comment

radcolor left a comment

Choose a reason for hiding this comment