ozone: ClientPixmapManager passes VGEM fd from browser to renderer.

content/browser/renderer_host/render_process_host_impl.cc

Index: content/browser/renderer_host/render_process_host_impl.cc
diff --git a/content/browser/renderer_host/render_process_host_impl.cc b/content/browser/renderer_host/render_process_host_impl.cc
index ff4f9869881ce4d4e3e62a73e012b588fa821d65..fff1663fb7c5d584c2720cce720230bc5a9bb25d 100644
--- a/content/browser/renderer_host/render_process_host_impl.cc
+++ b/content/browser/renderer_host/render_process_host_impl.cc
@@ -191,6 +191,7 @@
 #endif
 
 #if defined(USE_OZONE)
+#include "ui/ozone/public/client_native_pixmap_factory.h"
 #include "ui/ozone/public/ozone_switches.h"
 #endif
 
@@ -1601,6 +1602,10 @@ void RenderProcessHostImpl::OnChannelConnected(int32 peer_pid) {
           GetID());
   Send(new ChildProcessMsg_SetIOSurfaceManagerToken(io_surface_manager_token_));
 #endif
+#if defined(USE_OZONE)
+  int vgem_fd = ui::ClientNativePixmapFactory::GetInstance()->OpenVgemFD();

[reveman, 2015/08/14 13:19:12]

It's seems wrong that we ask the client factory to open a vgem fd. Should this
not be part of a more privileged API or at least be made a static function and
not part of the client side interface?

[dshwang, 2015/08/14 16:20:27]

spang, what do you think?
I chose ClientNativePixmapFactory because I wanted privileged API (i.e.
OzonePlatform) to be not aware of VGEM.
static function is not good because Ozone platform is chosen in run time. If I
implement it in static function, all Ozone platforms will know the API, which
mean all Ozone platforms become aware of "/dev/dri/renderD129".

As we encounter repeatedly, we need to make decision how much other Ozone
platforms are aware of vgem. In previous patch set, I made other platforms
consider it as "virtual_device".

+  Send(new ChildProcessMsg_SetVgemFD(base::FileDescriptor(vgem_fd, true)));
+#endif
 }
 
 void RenderProcessHostImpl::OnChannelError() {