If we set 2048KB ra value in the beginning of the
boot process, services initialized at this time would
keep 2048KB ra value even though we adjust the ra value
to 128KB after boot completion.
This may cause memory pressure.
Bug: 174700194
Signed-off-by: Randall Huang <huangrandall@google.com>
Change-Id: I97ee0ee9511eaada011f2634afd68d68cdca4570
This reverts commit b037c145f5ae958a7471edf95de5590f4a5f2575.
s2idle happens to cause RCU stalls. Disable it until a solution is found.
Change-Id: If0a6c817f415f6ddbdc202423492a7d2ebf1d0fb
* Used by GCAM for DSP-accelerated HDR processing
* Arguably we should label /vendor/dsp/cdsp/fastrpc_shell_3 to
same_process_hal_file like Pixels, but the partition is prebuilt thus
we're unable to relabel it.
* Copy the file to writable tmpfs, setup attributes and bind mount back
to workaround the limitation.
[ghostrider-reborn]:
Allow adsp/cdsprpcd and neuralnetworks HAL to access fastrpc_shell_3
[kras edit:
1. rename some contexts as per qva/kona
2. extend to allow camera HAL and VPP service to access it as well]
[dereference23: Remove VPP policy because atoll doesn't use it]
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Change-Id: Ide90e5c7307d413db5ece736e859559f06679545
sync ag/6911752,ag/9342439
fine tune the read_ahead size for boot time
Bug: 137150088
Bug: 139640385
Bug: 143448664
Test: boot to home and boot time measurement
Change-Id: If7929c51222e325a019532ce0d16045a52778165
Signed-off-by: Kyle Lin <kylelin@google.com>
Signed-off-by: Ocean Chen <oceanchen@google.com>
RD1A.200703.001
dmesg_action_sys.boot_completed_first_timestamp_avg : 14745.3
With CL
dmesg_action_sys.boot_completed_first_timestamp_avg : 13993.7
Bug: 143857500
Bug: 161478668
Test: build and boottime test
Tested-by: Lisa Liu <liulisa@google.com>
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: Ib8f31d39501b4747f0c268d2dd87e814bcc7843b
Because the arch is similiar with SDM670, we aling the setting with
bonito.
Bug: 142552311
Test: build , munaual check the settings
Change-Id: Ie4d4cd252cbe5cdaf733a8db09117808eb0ec27c
This patch removed the old writeout policy tune which was never touched since
2009. In the meantime, most of Android devices are equipped with over 4GB DRAM
and very fast flash storages like UFS, which becomes more like desktop or
servers in 2009. So, it'd be worth to go back to use the default kernel configs.
Bug: 136483670
Bug: 137190999
Bug: 152936751
Test: check value output
Change-Id: I1ebbf9f1f27a921103db51e96a50aadd6ec0dde8
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Signed-off-by: Martin Liu <liumartin@google.com>
Specifying avb=<vbmeta-partition> is only necessary for first entry of
partition groups that use same vbmeta partition. The following entry can have
<vbmeta-parititon> part omitted.
Test: None
Link: https://source.android.com/devices/architecture/kernel/mounting-partitions-early#fstab-entries
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I5a42fd3de72c400acfae56d6a1e1b85c22a79537
* "32-bit overflow" CAF mentioned in the function wrapper inside post-boot
script sounds very bs, since if it's 64-bit it won't be affected anyways
* We do the setup using fstab instead to allow setting up more flags such
as setting up backing device and compression streams; as such kanged from
Pixels
* zRAM size = 50% physical memory size to satisfy what CAF really wants
* Use LZ4 compression even for regular devices
Signed-off-by: Albert I <kras@raphielgang.org>
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
Change-Id: Ia6efb3d28e56fb026d9b28fc6633b2eac77dfa47
Build process errors out without this.
Traceback (most recent call last):
File "build/make/tools/releasetools/ota_from_target_files", line 2455, in <module>
main(sys.argv[1:])
File "build/make/tools/releasetools/ota_from_target_files", line 2429, in main
output_file=args[1])
File "build/make/tools/releasetools/ota_from_target_files", line 1103, in WriteFullOTAPackage
common.CheckSize(boot_img.data, "boot.img", target_info)
File "/home/aicp-dev/rom/lineage-17.1/build/make/tools/releasetools/common.py", line 1190, in CheckSize
p = info_dict["fstab"][mount_point]
KeyError: '/boot'
Change-Id: I30a396ea62e6e48420c0dd41533c156e90032929
init : Command 'mkdir /firmware 0771 system system' action=early-init (/vendor/etc/init/hw/init.target.rc:31) took 0ms and failed: Not a directory on /firmware
init : Command 'mkdir /bt_firmware 0771 system system' action=early-init (/vendor/etc/init/hw/init.target.rc:32) took 0ms and failed: Not a directory on /bt_firmware
init : Command 'mkdir /dsp 0771 media media' action=early-init (/vendor/etc/init/hw/init.target.rc:33) took 0ms and failed: Not a directory on /dsp
Signed-off-by: orgesified <me@orgesified.ml>
Change-Id: I129f6fd9210076fffa1912e3dd6dcec32bd5acf6
* /data/tombstones and /data/vendor/tombstones are both created by
the system's init.rc.
* Creating /tombstones at the root isn't allowed since the root is
a ramdisk and mounted read-only.
Change-Id: I04586994280ae48f36542f56e1cace422943376b
This should be done earlier:
libprocessgroup: Failed to open /dev/cpuset/camera-daemon/tasks: No such file or directory: No such file or directory
libprocessgroup: Failed to apply CameraServiceCapacity task profile: No such file or directory
Change-Id: I9edbdad2e764667a4624b181e0426f14ed9be616
* Remove unused/duplicated parts
* Make changes to do without other scripts
Co-authored-by: Demon000 <demonsingur@gmail.com>
Change-Id: I8e758337488dc19ecb47ec1b583fba33ef05882d
