Check mm_events persistent property after persistent properties are ready during boot.
Test: adb shell setprop persist.mm_events.enabled true; adb reboot \
adb shell ls /sys/kernel/tracing/instances/mm_events -> Exists
Fixes: 324600722
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:854ed748685ec65a232d84d32f4900e14e4b01be)
Merged-In: I091ca35f48e4baf8b6b5c24fba325f1dcae6b8b7
Change-Id: I091ca35f48e4baf8b6b5c24fba325f1dcae6b8b7
diff --git a/cmds/atrace/atrace.rc b/cmds/atrace/atrace.rc
index 3e6d2e0..a3e29a8 100644
--- a/cmds/atrace/atrace.rc
+++ b/cmds/atrace/atrace.rc
@@ -317,7 +317,7 @@
# Only create the tracing instance if persist.mm_events.enabled
# Attempting to remove the tracing instance after it has been created
# will likely fail with EBUSY as it would be in use by traced_probes.
-on post-fs-data && property:persist.mm_events.enabled=true
+on mm_events_property_available && property:persist.mm_events.enabled=true
# Create MM Events Tracing Instance for Kmem Activity Trigger
mkdir /sys/kernel/debug/tracing/instances/mm_events 0755 system system
mkdir /sys/kernel/tracing/instances/mm_events 0755 system system
@@ -402,6 +402,9 @@
chmod 0666 /sys/kernel/debug/tracing/instances/mm_events/per_cpu/cpu23/trace
chmod 0666 /sys/kernel/tracing/instances/mm_events/per_cpu/cpu23/trace
+on property:ro.persistent_properties.ready=true
+ trigger mm_events_property_available
+
# Handle hyp tracing instance
on late-init && property:ro.boot.hypervisor.vm.supported=1