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 addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
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
Disabling UFS clkgate and ah8 during boot time helps in reducing
IO delays, which helps in reducing the total boot time. This change
will disable UFS clkgate and ah8 during early-init and then enable
it back after boot completion.
Change-Id: I6a10cd57a30fe3bdc4fba72a0d84cdfa3b1fd513
Two fstabs are needed to support different data unit number (dun)
size for ufs and emmc hardwares. This needs different encryption
flag in fstab to address the difference in dun size.
[ArianK16a: don't add the emmc fstab since all our devices are ufs]
Test: Verified bootup, vts_kernel_encryption, fscryptctl.
Change-Id: Iff03422d39c789c544bdd86faef070ae46eb4e0e
Removing command to load ipa fw from post-fs, where FW mount
is not guaranteed.
Change-Id: I426bcfd2d9e0fb9f09a360374fe05b653676cf4b
CRs-Fixed: 2819603
QMCS partition is not a read only partition, and risks the danger
of causing unnecessary disk churn when QMCS files are read.
Update QMCS partition to be mounted with the noatime option.
Change-Id: Icf7e565d0e1c990131ad090c2f466bea419b4ad4
move spunvm partition out of fstab and mount in init.target.rc
only for lahaina as shima doesn't have spunvm partition.
Change-Id: I2b19c7cf84f23c0f73103fff2a2a7ae5a7dd186a
CRs-Fixed: 2801834
move sensors specific boot up commands from global init.qcom.rc to component
specific rc files , which are part of individual component projects.
Change-Id: Ib0410cd0af8d77573bd320063982b504b1b1d1d5
Remove context hub HAL service from common init rc file to
target specific
Change-Id: If32c8c15ad5e9ab4103db21580955bff6bfe92ef
Signed-off-by: Jeya R <jeyr@codeaurora.org>
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>
