Implement SingleThreadProxy CommitVSyncParameters

cc/trees/single_thread_proxy.cc

Index: cc/trees/single_thread_proxy.cc
diff --git a/cc/trees/single_thread_proxy.cc b/cc/trees/single_thread_proxy.cc
index 6498f0e0996ce49b310eb9a1c7a5d83bcfbfe4df..816050bb04ca6c9d3f058fec687140ee2a7429d5 100644
--- a/cc/trees/single_thread_proxy.cc
+++ b/cc/trees/single_thread_proxy.cc
@@ -463,6 +463,12 @@ void SingleThreadProxy::DidLoseOutputSurfaceOnImplThread() {
     scheduler_on_impl_thread_->DidLoseOutputSurface();
 }
 
+void SingleThreadProxy::CommitVSyncParameters(base::TimeTicks timebase,
+                                              base::TimeDelta interval) {
+  if (scheduler_on_impl_thread_)

[enne (OOO), 2014/12/15 19:25:15]

Actually, should this be a DCHECK? Does this get called by embedders not using
the scheduler? Or before the scheduler is created?

[brianderson, 2014/12/15 19:59:50]

I wouldn't expect this to get called before the scheduler is created.

However, I don't think there's logic in any of the many origins of this call
that considers what kind of cc::Proxy is used.

Either way, I don't think we need to make this a DCHECK. For configs where we
would hit the DCHECK, I don't see us caring about performance cost of a message
we don't listen to.

+    scheduler_on_impl_thread_->CommitVSyncParameters(timebase, interval);
+}
+
 void SingleThreadProxy::DidSwapBuffersOnImplThread() {
   TRACE_EVENT0("cc", "SingleThreadProxy::DidSwapBuffersOnImplThread");
   if (scheduler_on_impl_thread_)