Plumb cc::LatencyInfo through command buffer and output surface

content/common/gpu/image_transport_surface_mac.cc

Index: content/common/gpu/image_transport_surface_mac.cc
diff --git a/content/common/gpu/image_transport_surface_mac.cc b/content/common/gpu/image_transport_surface_mac.cc
index 8106f3bc52814fdf559d944a3d2fb8b08bb96a3a..abf9614439331abc7d53fafb2786baee757912cd 100644
--- a/content/common/gpu/image_transport_surface_mac.cc
+++ b/content/common/gpu/image_transport_surface_mac.cc
@@ -60,6 +60,7 @@ class IOSurfaceImageTransportSurface : public gfx::NoOpGLSurfaceCGL,
       const AcceleratedSurfaceMsg_BufferPresented_Params& params) OVERRIDE;
   virtual void OnResizeViewACK() OVERRIDE;
   virtual void OnResize(gfx::Size size) OVERRIDE;
+  virtual void SetLatencyInfo(const cc::LatencyInfo&) OVERRIDE;
 
  private:
   virtual ~IOSurfaceImageTransportSurface() OVERRIDE;
@@ -297,6 +298,11 @@ void IOSurfaceImageTransportSurface::OnResize(gfx::Size size) {
   CreateIOSurface();
 }
 
+void IOSurfaceImageTransportSurface::SetLatencyInfo(
+    const cc::LatencyInfo&) {
+  // TODO: implement

[piman, 2013/04/03 18:05:09]

Is there anything to do here beyond keeping it around and sending it with the
GpuHostMsg_AcceleratedSurfaceBuffersSwapped_Params message?

+}
+
 void IOSurfaceImageTransportSurface::UnrefIOSurface() {
   // If we have resources to destroy, then make sure that we have a current
   // context which we can use to delete the resources.