Add CPUBigClusterMaxFreq to Launch and Camera hints with higher priority
than Video Encode's hint value. In this case, Video Encode hint doesn't
need to be canceled during those hints.
Bug: 71869406
Test: Build
Change-Id: I53d17d32a8ff77257ba44cef7b8be2911b20b85f
On userdebug or eng, permit vdso to be enabled or disabled at will to
manage performance experiments on the dogfood population.
ro.debuggable=1 -> permit sys.vdso to maintain an influence over vdso
sys.vdso=false -> 32 and 64 bit vdso disabled
sys.vdso=32 -> 64 bit vdso disabled
sys.vdso=64 -> 32 bit vdso disabled
sys.vdso= -> 32 and 64 bit vdso enabled
NB: sys.vdso set to any other value will default to vdso enabled.
Test: manual, bionic-benchmarks --bionic_xml=vdso.xml to confirm.
Bug: 70518189
Change-Id: I839feff206a1404f228a5bdf35fb0c392fd8974a
There is a small chance that canceling Encode hint and enabling launch
at the same time. In this case, CPU max is capped so it need to be
updated first.
This CL will make PowerHAL updates max node first, in favor of boosting
hints, such as launch, camera shot and etc. When these boost hints end,
the performance limiting (power conserving) hint such as encode hint
could fail to set at the beginning but will succeed in the second try in
500ms.
Also change the rc file to let init do not restart PowerHAL when
framework died and there is no active long-lasting hint.
Bug: 67648152
Bug: 62041945
Test: launch camera
Test: kill cameraHAL, powerHAL, system-server
Change-Id: I4a9d8d395dea9f42cf6659c86635852f332f7617
PowerHAL should remember the long-lasting hint when it (re)starts,
in case it crashed/killed. Also when clint crashed, the long-lasting
hint should be cancelled.
This CL adds a property for PowerHAL to store its long-lasting hint,
and uses init to clear the property and restart PowerHAL when client
died.
Bug: 67648152
Test: kill cameraHAL, powerHAL, system-server
Change-Id: I6b2cae3c2228da00bcb97a3befacf9ab045eeba8
1) Add atrace into powerhint calls
2) Release encoder hint when placing camera and launch hint
Video Encode hint caps Big Cluster to 1.9G, so it will stop camera and launch hints setting Big
Cluster minfreq node to Max. If Video Encode hint is on, this CL will cancel it first and recover
it after camera/launch hints end.
Test: launch camera on walleye
Bug: 62041945
Change-Id: Ib278bdc55f58d5be9b2b4c2996c468bff5d71fbb
We recently created a new GID that can be granted to critical system
processes, so that the system is usable enough for the user to free
up disk space used by abusive apps.
128MB ought to be enough for anybody.
Test: builds, boots
Bug: 62024591
Change-Id: I54bfde3fb1a198f6f6c0e03c4bf21e48324ed8fc
PowerHAL (started in class hal) will try to reset nodes to their initial values,
however the node permission is granted only upon boot_complete which leads some
permission log spam. This CL is to address the logspam.
Test: boot and do powerhint
Bug: 62041945
Change-Id: I35ad8dfe23f35c829f50479ca951445afeb46b87
This is temporary, until we get the hardware implementation from
Qualcomm. When we do, this reference implementation will be replaced.
Until then, keystore will notice this implementation when starting up,
but favor the hardware keymaster 3.0 implementation. Engineers who
wish to do testing and development with the KM4 reference HAL on wahoo
can simply remove the hardware 3.0 implementation from the device.mk
file. Keystore will then find no HW implementation and will load the
SW implementation.
Test: Boot and run KM4 VTS tests.
Change-Id: I1b7183b221041b55792200a2aa3e0ed974da2e0b
This reverts commit aee1b828f7.
Configstore was up-revisioned from 1.0 to 1.1. However no new
APIs were added to 1.1. Therefore configstore in master will be down
revisioned to 1.0.
Bug: 71555815
Test: build & run
Change-Id: Ie441c505ccc17403e4e5450b3ac86a23f2272e8f
On wahoo devices we see bootloops due to failure to get KM4 HAL service
from hwservicemanager despite being running and registered.
This patch removes the reference KM4 HAL for now.
Test: N/A
Change-Id: I06cc6ce46d1fd754eefaff287e5e3cd8720507e3
