ozone: Introduce ClientPixmap and ClientPixmapFactory for non-GPU processes.

content/child/child_gpu_memory_buffer_manager.cc

 // Copyright 2014 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 "content/child/child_gpu_memory_buffer_manager.h"
 
 #include "content/common/child_process_messages.h"
 #include "content/common/gpu/client/gpu_memory_buffer_impl.h"
 
+#if defined(USE_OZONE)
+#include "ui/ozone/public/native_pixmap_client.h"
+#endif
+
 namespace content {
 namespace {
 
 void DeletedGpuMemoryBuffer(ThreadSafeSender* sender,
                             gfx::GpuMemoryBufferId id,
                             uint32 sync_point) {
   TRACE_EVENT0("renderer",
                "ChildGpuMemoryBufferManager::DeletedGpuMemoryBuffer");
   sender->Send(new ChildProcessHostMsg_DeletedGpuMemoryBuffer(id, sync_point));
 }
@@ skipping 13 matching lines @@
     const gfx::Size& size,
     gfx::GpuMemoryBuffer::Format format,
     gfx::GpuMemoryBuffer::Usage usage) {
   TRACE_EVENT2("renderer",
                "ChildGpuMemoryBufferManager::AllocateGpuMemoryBuffer",
                "width",
                size.width(),
                "height",
                size.height());
 
+#if defined(USE_OZONE)
+  ui::NativePixmapClient::InitializeIfNeeded();

[dshwang, 2015/06/03 14:11:51]

As you mentioned "The processes that want one will create one, and the processes
that don't need one won't.", this interface is initialized very lazily when it's
needed for Renderer.

[spang, 2015/06/05 19:21:53]

Lazy initialization leads to unpredictable initialization order.

Please do it eagerly and only once.

[reveman, 2015/06/05 20:26:06]

The MacOSX equivalent to NativePixmap is IOSurface and the child process wide
initialization of that is done in content/app/content_main_runner.cc. See
IOSurfaceManager::SetInstance. I think it would be best to do this
NativePixmapClient initialization at the same place.

[dshwang, 2015/06/08 11:15:14]

Done. Initialize it in render_thread_impl.cc, not content_main_runner.cc,
because gpu process doesn't need it.
btw, the interface doesn't use global or filescope object, so IMO this lazy
initialization isn't related to unpredictable initialization order.

+#endif
+
   gfx::GpuMemoryBufferHandle handle;
   IPC::Message* message = new ChildProcessHostMsg_SyncAllocateGpuMemoryBuffer(
       size.width(), size.height(), format, usage, &handle);
   bool success = sender_->Send(message);
   if (!success)
     return scoped_ptr<gfx::GpuMemoryBuffer>();
 
   scoped_ptr<GpuMemoryBufferImpl> buffer(GpuMemoryBufferImpl::CreateFromHandle(
       handle,
       size,
@@ skipping 14 matching lines @@
 }
 
 void ChildGpuMemoryBufferManager::SetDestructionSyncPoint(
     gfx::GpuMemoryBuffer* buffer,
     uint32 sync_point) {
   static_cast<GpuMemoryBufferImpl*>(buffer)
       ->set_destruction_sync_point(sync_point);
 }
 
 }  // namespace content