Adding support for VSyncProvider to the software drawing path

content/browser/aura/software_output_device_ozone.cc

Index: content/browser/aura/software_output_device_ozone.cc
diff --git a/content/browser/aura/software_output_device_ozone.cc b/content/browser/aura/software_output_device_ozone.cc
index c704fedc85e566098d045d9b8e5bfbfb789e1f39..e8a57b583d1864cd85e2f45b9cebea85ef92a240 100644
--- a/content/browser/aura/software_output_device_ozone.cc
+++ b/content/browser/aura/software_output_device_ozone.cc
@@ -31,13 +31,12 @@ void SoftwareOutputDeviceOzone::Resize(gfx::Size viewport_size) {
   gfx::SurfaceFactoryOzone* factory = gfx::SurfaceFactoryOzone::GetInstance();
   factory->AttemptToResizeAcceleratedWidget(compositor_->widget(),
                                             bounds);
-  gfx::AcceleratedWidget realized_widget = factory->RealizeAcceleratedWidget(
-      compositor_->widget());
+  realized_widget_ = factory->RealizeAcceleratedWidget(compositor_->widget());

[piman, 2013/11/05 23:32:27]

Could this be done at construction time?

 
-  if (realized_widget == gfx::kNullAcceleratedWidget)
+  if (realized_widget_ == gfx::kNullAcceleratedWidget)
     LOG(FATAL) << "Failed to get a realized AcceleratedWidget";
 
-  canvas_ = skia::SharePtr(factory->GetCanvasForWidget(realized_widget));
+  canvas_ = skia::SharePtr(factory->GetCanvasForWidget(realized_widget_));
   device_ = skia::SharePtr(canvas_->getDevice());
 }
 
@@ -66,4 +65,9 @@ void SoftwareOutputDeviceOzone::EndPaint(cc::SoftwareFrameData* frame_data) {
   DCHECK(scheduled) << "Failed to schedule pageflip";
 }
 
+gfx::VSyncProvider* SoftwareOutputDeviceOzone::GetVSyncProvider() {
+  return gfx::SurfaceFactoryOzone::GetInstance()->GetVSyncProvider(
+      realized_widget_);

[piman, 2013/11/05 23:32:27]

Do we expect different VSyncProvider across calls? Should we cache it at
construction time?

+}
+
 }  // namespace content