Commit 889afc2c authored by Sami Kyostila's avatar Sami Kyostila Committed by Commit Bot

Remove trace event category warming

Since all categories are now statically defined, there's no need to warm
any of them up explicitly in order for the categories to show up in the
tracing UI.

Depends on https://chromium-review.googlesource.com/c/chromium/src/+/1401273

[email protected]

Bug: 914579
Change-Id: Idbabec3fa9e3f35716663d08260691d7bf4ecfa7
Reviewed-on: https://chromium-review.googlesource.com/c/1402760Reviewed-by: default avatarSami Kyöstilä <[email protected]>
Reviewed-by: default avatarEric Seckler <[email protected]>
Reviewed-by: default avataroysteine <[email protected]>
Commit-Queue: Sami Kyöstilä <[email protected]>
Cr-Original-Commit-Position: refs/heads/[email protected]{#621979}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: eb0e029a36e458f83480607531122dd514f4ded7
parent 211b3ed9
......@@ -1005,14 +1005,6 @@
} \
} while (0)
// Macro to explicitly warm up a given category group. This could be useful in
// cases where we want to initialize a category group before any trace events
// for that category group is reported. For example, to have a category group
// always show up in the "record categories" list for manually selecting
// settings in about://tracing.
#define TRACE_EVENT_WARMUP_CATEGORY(category_group) \
INTERNAL_TRACE_EVENT_GET_CATEGORY_INFO(category_group)
// Macro to efficiently determine, through polling, if a new trace has begun.
#define TRACE_EVENT_IS_NEW_TRACE(ret) \
do { \
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment