cc: Add threaded GPU rasterization.

cc/output/output_surface.cc

 // Copyright (c) 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "cc/output/output_surface.h"
 
 #include "base/bind.h"
 #include "base/message_loop/message_loop.h"
 #include "base/trace_event/trace_event.h"
 #include "cc/output/managed_memory_policy.h"
@@ skipping 116 matching lines @@
     }
   }
 
   if (!success)
     client_ = NULL;
 
   return success;
 }
 
 bool OutputSurface::InitializeAndSetContext3d(
-    scoped_refptr<ContextProvider> context_provider) {
+    scoped_refptr<ContextProvider> context_provider,
+    scoped_refptr<ContextProvider> worker_context_provider) {
   DCHECK(!context_provider_.get());
   DCHECK(context_provider.get());
   DCHECK(client_);
 
-  bool success = false;
-  if (context_provider->BindToCurrentThread()) {
+  bool success = context_provider->BindToCurrentThread();
+  if (success) {
     context_provider_ = context_provider;
     SetUpContext3d();
-    client_->DeferredInitialize();
-    success = true;
+  }
+  if (success && worker_context_provider.get()) {
+    success = worker_context_provider->BindToCurrentThread();

[boliu, 2015/02/13 20:25:52]

Was trying this in webview with a ganesh page, and failed in a thread check in
ContextProviderInProcess::ContextGL.

This method is called on the thread, so we can't bind the worker context here
and then use it on a worker thread.

But InitializeAndSetContext3d needs to synchronous return false if this fails.
I'm not sure if it's possible to block the compositor thread on worker threads?

[vmiura, 2015/02/13 21:28:32]

I think I need to implement ContextProviderInProcess::DetachFromThread(), as we
did for ContextProviderCommandBuffer::DetachFromThread().

+    if (success) {
+      worker_context_provider_ = worker_context_provider;
+      // The destructor resets the context lost callback, so base::Unretained
+      // is safe, as long as the worker threads stop using the context before
+      // the output surface is destroyed.
+      worker_context_provider_->SetLostContextCallback(base::Bind(

[boliu, 2015/02/13 20:25:52]

Same threading problem on the context loss callback I think.

[vmiura, 2015/02/13 21:28:32]

Same here.

We bind to the compositor thread here, but then GpuTileTaskWorkerPool
constructor calls ContextProvider::DetachFromThread() to take ownership, and
again in it's destructor to release ownership.

+          &OutputSurface::DidLoseOutputSurface, base::Unretained(this)));
+    }
   }
 
   if (!success)
     ResetContext3d();
+  else
+    client_->DeferredInitialize();
 
   return success;
 }
 
 void OutputSurface::ReleaseGL() {
   DCHECK(client_);
   DCHECK(context_provider_.get());
   client_->ReleaseGL();
   DCHECK(!context_provider_.get());
 }
@@ skipping 83 matching lines @@
   TRACE_EVENT1("cc", "OutputSurface::SetMemoryPolicy",
                "bytes_limit_when_visible", policy.bytes_limit_when_visible);
   // Just ignore the memory manager when it says to set the limit to zero
   // bytes. This will happen when the memory manager thinks that the renderer
   // is not visible (which the renderer knows better).
   if (policy.bytes_limit_when_visible)
     client_->SetMemoryPolicy(policy);
 }
 
 }  // namespace cc