Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix enable checks to check use action in LatencyTracker

Browse Source 
Without checking the per-action enable, logging is only allowed
based on the global enable flag instead of the enable flag per action.
Checking the per-action enable flag allows for action latencies to be
rolled out independent of each other.

Test: manual verify action is logged with only action specific enable
set
Bug: 265850090

Change-Id: I4f8d21bca4a9e52fb3875e88387b8c8641f64c94
Merged-In: I4f8d21bca4a9e52fb3875e88387b8c8641f64c94
This commit is contained in:
Nicholas Ambur
2023-03-22 14:59:21 +00:00
parent c37e3adeff
commit ca9e12eec9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
core/java/com/android/internal/util/LatencyTracker.java
View File

@@ -471,7 +471,7 @@ public class LatencyTracker {
*/ */
public void onActionStart(@Action int action, String tag) { public void onActionStart(@Action int action, String tag) {
synchronized (mLock) { synchronized (mLock) {
if (!isEnabled()) { if (!isEnabled(action)) {
return; return;
} }
// skip if the action is already instrumenting. // skip if the action is already instrumenting.
@@ -495,7 +495,7 @@ public class LatencyTracker {
*/ */
public void onActionEnd(@Action int action) { public void onActionEnd(@Action int action) {
synchronized (mLock) { synchronized (mLock) {
if (!isEnabled()) { if (!isEnabled(action)) {
return; return;
} }
Session session = mSessions.get(action); Session session = mSessions.get(action);