Merge Group Markers into Chromium Traces.

cc/resources/scoped_gpu_raster.cc

Index: cc/resources/scoped_gpu_raster.cc
diff --git a/cc/resources/scoped_gpu_raster.cc b/cc/resources/scoped_gpu_raster.cc
index 2f5c5c9c3426a42eca7532cb8919611884a983d1..db8e9985c2f58137539da29ee46c7d80c426e125 100644
--- a/cc/resources/scoped_gpu_raster.cc
+++ b/cc/resources/scoped_gpu_raster.cc
@@ -28,6 +28,7 @@ void ScopedGpuRaster::BeginGpuRaster() {
   // Using push/pop functions directly incurs cost to evaluate function
   // arguments even when tracing is disabled.
   gl->PushGroupMarkerEXT(0, "GpuRasterization");
+  gl->TraceBeginCHROMIUM("GroupMarker", "GpuRasterization");

[no sievers, 2015/05/12 17:51:44]

Why "GroupMarker"?

[David Yen, 2015/05/12 17:56:13]

I couldn't really think of a good trace category, maybe just ScopedGpuRaster?

 
   class GrContext* gr_context = context_provider_->GrContext();
   gr_context->resetContext();
@@ -45,6 +46,7 @@ void ScopedGpuRaster::EndGpuRaster() {
   // TODO(alokp): Use a trace macro to push/pop markers.
   // Using push/pop functions directly incurs cost to evaluate function
   // arguments even when tracing is disabled.
+  gl->TraceEndCHROMIUM();
   gl->PopGroupMarkerEXT();
 }