summaryrefslogtreecommitdiff
path: root/tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
diff options
context:
space:
mode:
authorCody Northrop <cnorthrop@google.com>2019-01-15 14:06:36 -0700
committerCody Northrop <cnorthrop@google.com>2019-01-24 07:06:37 -0700
commit5ebb0db1043f71ca785396ca98047639e7627e99 (patch)
tree6cab3c62a39635dfe0ad29b21843cd76dcc26924 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
parentb959de1a9435312a2a15afbcd720c8829333a7e5 (diff)
Guard ANGLE rules checking with a whitelist
In order to reduce the startup impact to near zero, we are creating a whitelist to be checked before parsing rules. The whitelist will be generated by the APK based on apps mentioned in the rules files. At app launch, only those in the whitelist will do full rules checking. The whitelist will be checked via Global Settings, which will be populated by the ANGLE APK when intents are received. The APK will listen for intents at boot (LOCKED_BOOT_COMPLETED) and when ANGLE itself is updated (MY_PACKAGE_REPLACED). The whitelist can also be populated by hand: adb shell settings put global angle_whitelist app1,app2,appN We plan to further mitigate the ANGLE-enabled app impact by parsing the full rules when creating the whitelist, off of the critical path. Note: Developer Options will continue to work, regardless of whitelist. But temp rules will not be loaded if the app is not whitelisted. Test: atest CtsAngleIntegrationHostTestCases Test: atest google/perf/app-startup/hermetic-apps/cold-dropcache-test -v Bug: 80239516 Bug: 122528316 Change-Id: I96e5b4d5b4774f59aadbd1e52295437a395cab6b
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions