Trace Redaction - Frame Timeline
Screen updates are communicated using frame_timeline_event packets.
These packets fall into one of five types:
1. expected display frame start (pid + cookie)
2. actual display frame start (pid + cookie)
3. expected surface frame end (pid + cookie)
4. expected surface frame end (pid + cookie)
5. frame end (cookie)
Start events are end events are connected through their cookie values.
Because cookie saves are unique across the whole trace, it is safe to
assume that 'frame end' with cookie C matches 'frame start' with
cookie C.`
Frame events will appears for a little number of processes. They
always appear for surface flinger, and they will optionally appear
with an app. As implemented, only events from the target package are
retained.
Bug: 333404689
Change-Id: Iabff83549874f1bfbd3875d2ae3cff1a26b68e83
diff --git a/Android.bp b/Android.bp
index 6cb0053..5de15e2 100644
--- a/Android.bp
+++ b/Android.bp
@@ -12891,6 +12891,7 @@
filegroup {
name: "perfetto_src_trace_redaction_trace_redaction",
srcs: [
+ "src/trace_redaction/collect_frame_cookies.cc",
"src/trace_redaction/collect_timeline_events.cc",
"src/trace_redaction/filter_ftrace_using_allowlist.cc",
"src/trace_redaction/filter_packet_using_allowlist.cc",
@@ -12921,6 +12922,7 @@
filegroup {
name: "perfetto_src_trace_redaction_unittests",
srcs: [
+ "src/trace_redaction/collect_frame_cookies_unittest.cc",
"src/trace_redaction/collect_timeline_events_unittest.cc",
"src/trace_redaction/filter_ftrace_using_allowlist_unittest.cc",
"src/trace_redaction/filter_packet_using_allowlist_unittest.cc",
