Infrastructure for temportarily relinquishing GPU resources.

ui/ozone/common/gpu/ozone_gpu_messages.h

Index: ui/ozone/common/gpu/ozone_gpu_messages.h
diff --git a/ui/ozone/common/gpu/ozone_gpu_messages.h b/ui/ozone/common/gpu/ozone_gpu_messages.h
index c98f153e44ada833921355919f3406042141e0c0..fa83cdf02edd0117a6b435e6be05de261b3385f0 100644
--- a/ui/ozone/common/gpu/ozone_gpu_messages.h
+++ b/ui/ozone/common/gpu/ozone_gpu_messages.h
@@ -99,6 +99,10 @@ IPC_MESSAGE_CONTROL0(OzoneGpuMsg_TakeDisplayControl)
 // Let other entity control the display
 IPC_MESSAGE_CONTROL0(OzoneGpuMsg_RelinquishDisplayControl)
 
+// Tells the GPU process to relinquish the display to an external process.
+// Creating a new surface will automatically re-acquire the display.
+IPC_MESSAGE_CONTROL0(OzoneGpuMsg_RelinquishDisplay)

[piman, 2014/11/18 20:55:34]

Where is the code that uses this new message?

[GusFernandez, 2014/11/19 18:50:13]

This and OzoneHostMsg_ResourcesRelinquished below are used to communicate
between the browser and GPU processes by the internal Cast ozone_platform which
has vendor-specific code which we cannot open-source.

[piman, 2014/11/19 20:33:52]

I'm not a big fan of adding messages that have no (visible) users, nor an
implementation. For the purpose of the chromium project, it has no value.

I like spang@'s suggestion. A single cross-platform message that does generic
cleanup as well as platform-specific cleanup. The platform specifics is hidden
behind an ozone API.

+
 //------------------------------------------------------------------------------
 // Browser Messages
 // These messages are from the GPU to the browser process.
@@ -106,3 +110,6 @@ IPC_MESSAGE_CONTROL0(OzoneGpuMsg_RelinquishDisplayControl)
 // Updates the list of active displays.
 IPC_MESSAGE_CONTROL1(OzoneHostMsg_UpdateNativeDisplays,
                      std::vector<ui::DisplaySnapshot_Params>)
+
+// Response to OzoneGpuMsg_RelinquishDisplay
+IPC_MESSAGE_CONTROL0(OzoneHostMsg_ResourcesRelinquished)