+21
−46
+5
−0
Loading
Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more
This reverts commit dc340974. "Revert "Set the atrace clock to boot when possible and mono otherwise."" ...and includes a fix for devices that break with that change. Write will fail with an Invalid Argument exception if we programmatically write a value to the trace_file that doesn't exist in the file. So, we'll check for both potential values we might set. If neither of them exist, fall back to setting to 'global', which should be safe since we were doing it before without checking. Bug: 32379831 Test: cts-tradefed run singleCommand cts-dev --module CtsAtraceHostTestCases passed. Test: Manually examining trace_clock before and after running atrace shows that the trace_clock changes as expected (for this test I disabled atrace.rc and added an additional debug print statement): $ cat /d/tracing/trace_clock [local] global counter uptime perf mono boot $ atrace --async_start freq capturing trace...marlin:/ $ cat /d/tracing/trace_clock local global counter uptime perf mono [boot] $ atrace --async_stop > /dev/null $ cat /d/tracing/trace_clock local global counter uptime perf mono [boot] $ atrace --async_start freq clock is already correct! $ atrace --async_stop > /dev/null Change-Id: I267056d19bcdbea58881ab2b32f093caac5f14c1