Update list of which Chrome categories to trace

In crrev.com/c/1052130 one of the Chrome tracing categories was renamed. This change aligns the UIforETW UI to match Chrome. In crrev.com/c//1134516 support was added for ETW tracing of Chrome's "latency" category and this change adds UIforETW support. This is an extremely useful (low-bandwidth, performance analysis relevant) category which I'm now going trace by default.
google · Jul 15, 2018 · b8f52da · b8f52da
1 parent 88c4270
commit b8f52da
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/UIforETW/Settings.cpp b/UIforETW/Settings.cpp
@@ -49,13 +49,14 @@ const PCWSTR filtered_event_group_names[] =
 	L"gpu",                                             // 0x20
 	L"input",                                           // 0x40
 	L"netlog",                                          // 0x80
-	L"renderer.scheduler",                              // 0x100
+	L"sequence_manager",                                // 0x100
 	L"toplevel",                                        // 0x200
 	L"v8",                                              // 0x400
 	L"disabled-by-default-cc.debug",                    // 0x800
 	L"disabled-by-default-cc.debug.picture",            // 0x1000
 	L"disabled-by-default-toplevel.flow",               // 0x2000
 	L"startup",                                         // 0x4000
+	L"latency",                                         // 0x8000
 };
 
 // 1ULL << 61 and 1ULL << 62 are special values that indicate to Chrome to