Enable Surfaces on Android (try #3)

Enable Surfaces on Android (try #3)

The browser compositor contents and renderer contents are each put into separate Surfaces which are aggregated together by a Display.

BUG=449319
Committed: https://crrev.com/8da5f9f03e955304716977004fd4ba1168869aca
Cr-Commit-Position: refs/heads/master@{#320826}

[jbauman, 2015-03-13 22:02:09]

jbauman@chromium.org changed reviewers:
+ sievers@chromium.org

[no sievers, 2015-03-13 23:07:16]

lgtm :)

[jbauman, 2015-03-16 21:56:16]

The CQ bit was checked by jbauman@chromium.org

[commit-bot: I haz the power, 2015-03-16 21:56:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1001203002/1

[commit-bot: I haz the power, 2015-03-17 00:05:51]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-03-17 00:06:30]

Patchset 1 (id:??) landed as
https://crrev.com/8da5f9f03e955304716977004fd4ba1168869aca
Cr-Commit-Position: refs/heads/master@{#320826}

[fmeawad, 2015-03-17 17:58:04]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1015813002/ by fmeawad@chromium.org.

The reason for reverting is: Speculative revert as it seems to be causing a big
regression in input_latency/thread_time_cpu_per_frame

BUG=467978.