From 69915f973399a8b4e948877ce0cadead1e1a577a Mon Sep 17 00:00:00 2001 From: Carmen Jackson Date: Tue, 23 May 2017 11:54:01 -0700 Subject: [PATCH] Do not set the trace clock in atrace.rc. This reverts only the atrace.rc change from commit ea826794184be368f65f099ceac4fc31234700f6. "Set the atrace clock to the best available value: boot, mono, or global." This change caused a 100+ms regression in boot time. We also confirm that the clock is set to the correct value when we call atrace, so we will still see correct behavior after reverting this change. Bug: 38504158 Test: Manually tested that the trace clock is updated when atrace is called. Change-Id: Ifa302694964a4f9fc54db16e7125d5279067bbfd --- cmds/atrace/atrace.rc | 5 ----- 1 file changed, 5 deletions(-) diff --git a/cmds/atrace/atrace.rc b/cmds/atrace/atrace.rc index 52f3339e18..cef41bebf4 100644 --- a/cmds/atrace/atrace.rc +++ b/cmds/atrace/atrace.rc @@ -124,11 +124,6 @@ on post-fs write /sys/kernel/debug/tracing/tracing_on 0 write /sys/kernel/tracing/tracing_on 0 - # Set the trace clock to boot; falling back to mono or boot - write /d/tracing/trace_clock global - write /d/tracing/trace_clock mono - write /d/tracing/trace_clock boot - # Allow only the shell group to read and truncate the kernel trace. chown root shell /sys/kernel/debug/tracing/trace chown root shell /sys/kernel/tracing/trace -- 2.11.0