Implement service-side surface synchronization

cc/ipc/compositor_frame_metadata.mojom

Index: cc/ipc/compositor_frame_metadata.mojom
diff --git a/cc/ipc/compositor_frame_metadata.mojom b/cc/ipc/compositor_frame_metadata.mojom
index 992f53d40f683436594d6cc4578e5aaf4ac374b2..8345b4dc360b315fc5cd5fdbc0af6dfae8d89cd9 100644
--- a/cc/ipc/compositor_frame_metadata.mojom
+++ b/cc/ipc/compositor_frame_metadata.mojom
@@ -30,4 +30,5 @@ struct CompositorFrameMetadata {
   Selection selection;
   array<ui.mojom.LatencyInfo> latency_info;
   array<SurfaceId> referenced_surfaces;
+  bool respect_deadline;

[vmpstr, 2017/02/07 22:46:19]

As an aside, should there some ordering to these variables with respect to
types? I'm not sure how mojo structs work, but in C++ for example (on my
machine)

struct {
 bool b1;
 int i;
 bool b2;
};

is 12 bytes, where as

struct {
 int i;
 bool b1;
 bool b2;
};

is 8 bytes. (padding ftl).

[Fady Samuel, 2017/02/08 00:52:48]

Yes, we should probably move all bools to the bottom, but I won't do it in this
CL to confuse matters.

 };