During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: Ide78be316778acfc5c582c4a7b78853796cf4c1e
Revert submission 26822004
Reason for revert: Potential culprit for b/339099720- verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:26822004
Change-Id: Ie9598a3b3b56c8ce26f475079798c44314696f44
During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: I4c4024b4cad18199226f5644f98254b2230574d6
Next CLs in this stack will make changes to persist/efs mount process
This CL will first move relevant code to a separate file for easier
review.
To support booting under 16K page size, we need to copy files on
persist partition(F2FS, which does not support 16K page size)
to data partition(which will would be EXT4 for dev option enabled
devices).
Bug: 319335586
Change-Id: I2750eb8b53431037cecc972448799409345f5ca3
From field data, sometimes kcompactd is
pretty activated and can impact critical
CUJs. Disable it first to mitigate the
impact.
Bug: 332916849
Test: boot
Change-Id: I87cdcf184afb5fe10e873162b94bd3bf54b1acbd
Signed-off-by: Martin Liu <liumartin@google.com>
DisplayPort kernel driver passes error code/status to hardware composer
via the dp_hotplug_error_code sysfs file. When HWC receives/consumes
the error, it will write "0" into that file to reset the error code. So
this file must be readable and writable by the HWC code running with
"system" user/group permissions.
Previously we used to set the ownership to system:system, but in order
to be more consistent with the rest of sysfs files in that directory,
we can use root:graphics instead with permissions 0664. HWC runs
under the "graphics" group, so this should allow HWC write access.
Bug: 324953626
Test: checked permissions of dp_hotplug_error_code sysfs
Change-Id: Idf65acc12d158a78565c41f4e2aea24362e2cdff
We have observed more reclaiming activities as upstream
has changed how PCP high is calculated since 5.15 kernel.
Re-align the level back to 5.10 first so we can monitor
how it impacts the MM metrics.
Bug: 309409009
Test: boot
Change-Id: I7ac1eb88a8dae7c823330a2c75aec9547bd5c427
Signed-off-by: Martin Liu <liumartin@google.com>
Vendor sched procfs path hierarchy gets updated in kernel.
Update the paths in init rc file and task profiles to match the change.
Bug: 289151587
Test: pts-tradefed run commandAndExit pts -m PtsPerfWbsTestCases
-t com.google.android.perfwbs.pts.SchedulerTest
Change-Id: I14d07c4525f4bf60318bca31a89b9130c4236600
The values are based on most efficient frequencies from EM default
profile.
Bug: 289083704
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: Iab3f17c9f32e0ea01e1a8f414373aac0fece8b46
Change the owner and group of the DRM module debug file to system to
grant permission for hwcomposer.
Bug: 301599195
Test: check HWC can access it
Change-Id: I985c402bc2d920a43493dddd73e9470ab0228104
dp_hotplug_error_code owner needs to be the system user, since HWC
needs to be able to write into it, to reset the error code.
Test: manual
Bug: 283461313
Change-Id: I0866e39f3cd75878628d44b4afaf53df61448213
This reverts commit 253d3d48fa.
Reason for revert: Scheduling while atomic b/301031609
Bug: 301031609
Change-Id: I8179a926315da55ede03653a1517f13f61f3fdeb
There are power regression reports for low activity use cases on mids
and bigs. Disable util-awareness on mids and bigs for now until this is
better investigated and either use a slightly higher threshold or fix
any potential root cause that is causing unnecessary higher activities
on these cores.
Bug: 289293494
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I7ab2dca998c749567c5e1908d57b2174313e8390
(cherry picked from commit 4c559d3334)
