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

content/common/gpu/native_pixmap_manager_ozone_messages.h

Index: content/common/gpu/native_pixmap_manager_ozone_messages.h
diff --git a/content/common/gpu/native_pixmap_manager_ozone_messages.h b/content/common/gpu/native_pixmap_manager_ozone_messages.h
new file mode 100644
index 0000000000000000000000000000000000000000..33b1ab5b280496d418daea640d26704d6bcf2d15
--- /dev/null
+++ b/content/common/gpu/native_pixmap_manager_ozone_messages.h
@@ -0,0 +1,18 @@
+// Copyright 2015 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.
+
+#ifndef CONTENT_COMMON_COMMON_GPU_NATIVE_PIXMAP_MANAGER_OZONE_MESSAGES_H_
+#define CONTENT_COMMON_COMMON_GPU_NATIVE_PIXMAP_MANAGER_OZONE_MESSAGES_H_
+
+#include "base/file_descriptor_posix.h"
+#include "ipc/ipc_message_macros.h"
+
+#define IPC_MESSAGE_START BrowserNativePixmapManagerMsgStart
+
+// Messages sent to BrowserNativePixmapManager.
+// Asks the browser to reply virtual device fd.
+IPC_SYNC_MESSAGE_CONTROL0_1(BrowserNativePixmapManagerMsg_SyncGetVirtualDevice,

[dshwang, 2015/07/06 18:45:01]

Done. renamed.
I couldn't find the way. BrowserIOSurfaceManager::Initialize registers mach
token into kernel, and then BrowserIOSurfaceManager::LookupServicePort in
renderer looks up the token from kernel.
In this sense, Browser needs to register VGEM FD into linux kernel. There is no
way. In addition, Browser and Renderer cannot communicate until the channel is
connected (i.e. ChildThreadImpl::OnChannelConnected())

+                            base::FileDescriptor /* device_fd */)
+
+#endif  // CONTENT_COMMON_COMMON_GPU_NATIVE_PIXMAP_MANAGER_OZONE_MESSAGES_H_