arc: Use limited set of systrace events in tracing tool.

Now it is possible to define exact set of sys events to trace. This CL
utilizes this functionality in order to reduce footprint on memory usage
and speedup tracing analysis.

TEST=Locally, tracing tool works as expected
BUG=b:140939504

Change-Id: Ibceca4d372a368bc07a38812f9c87381199c51d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816798
Commit-Queue: Yury Khmel <khmel@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#698633}

chrome/browser/ui/webui/chromeos/arc_graphics_tracing/arc_graphics_tracing_handler.cc

@@ -407,6 +407,13 @@ void ArcGraphicsTracingHandler::StartTracing() {
       "gfx,disabled-by-default-android hal,disabled-by-default-android view",
       base::trace_event::RECORD_CONTINUOUSLY);
   config.EnableSystrace();
+  // By default, systracing starts pre-defined set of categories with predefined
+  // set of events in each category. Limit events to what we actually analyze in
+  // ArcTracingModel.
+  config.EnableSystraceEvent("i915:intel_gpu_freq_change");
+  config.EnableSystraceEvent("power:cpu_idle");
+  config.EnableSystraceEvent("sched:sched_wakeup");
+  config.EnableSystraceEvent("sched:sched_switch");
   tracing_active_ = true;
   if (jank_detector_)
     jank_detector_->Reset();