Plumb GpuMemoryBuffer allocation to GPU process.

content/browser/renderer_host/render_message_filter.cc

Index: content/browser/renderer_host/render_message_filter.cc
diff --git a/content/browser/renderer_host/render_message_filter.cc b/content/browser/renderer_host/render_message_filter.cc
index 03d8b40e4b14430fd6733c15c30bf3e78c833691..54d27a4fa3c0b4f25d4d900cfb61dbf931209498 100644
--- a/content/browser/renderer_host/render_message_filter.cc
+++ b/content/browser/renderer_host/render_message_filter.cc
@@ -20,6 +20,7 @@
 #include "content/browser/dom_storage/dom_storage_context_wrapper.h"
 #include "content/browser/dom_storage/session_storage_namespace_impl.h"
 #include "content/browser/download/download_stats.h"
+#include "content/browser/gpu/browser_gpu_channel_host_factory.h"
 #include "content/browser/gpu/gpu_data_manager_impl.h"
 #include "content/browser/loader/resource_dispatcher_host_impl.h"
 #include "content/browser/media/media_internals.h"
@@ -1322,6 +1323,27 @@ void RenderMessageFilter::OnAllocateGpuMemoryBuffer(uint32 width,
   }
 #endif
 
+#if 0
+  gfx::GpuMemoryBufferParams params;
+  params.width = width;
+  params.height = height;
+  params.internalformat = internalformat;
+  params.usage = usage;
+
+  BrowserGpuChannelHostFactory* factory =
+      BrowserGpuChannelHostFactory::instance();
+  BrowserThread::PostTask(
+      BrowserThread::UI,
+      FROM_HERE,
+      base::Bind(
+          &BrowserGpuChannelHostFactory::AllocateGpuMemoryBufferAsync,
+          base::Unretained(factory),
+          params,
+          base::Bind(
+              &RenderMessageFilter::GpuMemoryBufferAllocated, this, reply)));
+  return;

[reveman, 2014/05/27 22:46:01]

This should be hidden in the specific GpuMemoryBufferImpl implementation that
needs to create the buffer on the GPU process side.

How about we define a separate interface for Create/DestroyGpuMemoryBuffer? The
same instance that implements BrowserGpuChannelHostFactory can implement this
interface on the browser process side. There wouldn't be anything browser
process specific about this interface though. It would live in content/common
but only implemented on the browser side.

GpuMemoryBufferImpl implementations can use it for buffer allocation whenever
the interface is implemented.

[alexst (slow to review), 2014/05/28 14:18:57]

This was just a bit of stub code to make sure everything compiled.

Sounds good on the new interface. I'll get to coding.

+#endif
+
   GpuMemoryBufferImpl::AllocateForChildProcess(
       gfx::Size(width, height),
       internalformat,