Add initial GpuMemoryBufferSurfaceTexture implementation.

content/browser/renderer_host/compositor_impl_android.h

Index: content/browser/renderer_host/compositor_impl_android.h
diff --git a/content/browser/renderer_host/compositor_impl_android.h b/content/browser/renderer_host/compositor_impl_android.h
index 15a16b34d1d2c4d9ba1182c9803febc468d24f8c..06882733a1b0f17d1be16bcc64f40c7eb009e109 100644
--- a/content/browser/renderer_host/compositor_impl_android.h
+++ b/content/browser/renderer_host/compositor_impl_android.h
@@ -49,6 +49,15 @@ class CONTENT_EXPORT CompositorImpl
   // Returns the Java Surface object for a given view surface id.
   static jobject GetSurface(int surface_id);
 
+  // Returns the Java Surface object for a given surface texture.
+  static jobject GetSurfaceTextureSurface(int primary_id, int secondary_id);

[no sievers, 2014/03/24 19:26:08]

Why did you follow the bad example from the existing EstablishPeer code and
changed the variable names to be so generic? :)


Could it just be |surface_texture_id| and |child_process_id| or something like
that?

[reveman, 2014/03/25 01:31:23]

Changed it to an explicit base::ProcessHandle where I think is appropriate in
latest patch. I kept the detail that we use a process handle as part of the id
hidden from the renderer side and from the ui/gl/ code. I prefer if this is only
exposed to the code that depends on it. That's content/browser,
content/common/gpu/gpu_command_buffer_stub.cc and
content/public/android/java/src/org/chromium/content/browser.

Does that make sense?

+
+  // Allocates a surface texture and returns primary id. Returns -1 on failure.
+  static int AllocateSurfaceTexture(int secondary_id);
+
+  // Destroy all surface textures associated with |secondary_id|.
+  static void DestroyAllSurfaceTextures(int secondary_id);
+
   // Compositor implementation.
   virtual void SetRootLayer(scoped_refptr<cc::Layer> root) OVERRIDE;
   virtual void SetWindowSurface(ANativeWindow* window) OVERRIDE;