Pass more frame timing information to Blink

Pass more frame timing information to Blink

This patch conveys more information about frame timings to Blink.
Specifically it adds the current deadline by which work should be
finished as well as the expected interval between frames. The
Blink scheduler will use this information to schedule lower priority
work.

We also notify Blink when a committed frame actually got composited,
which means the current frame is done and lower priority work can be
started immediately (i.e., before the scheduled deadline).

BUG=391005
Committed: https://crrev.com/7759d7aef4c97d3454c15607945e23595c2dfa3e
Cr-Commit-Position: refs/heads/master@{#293476}

[Sami, 2014-08-29 11:52:32]

skyostil@chromium.org changed reviewers:
+ jamesr@chromium.org

[Sami, 2014-08-29 11:54:00]

(Depends on https://codereview.chromium.org/516103003/)

[Sami, 2014-09-02 14:01:18]

Excuse the spam, but for some reason it looks like the above message never got
sent.

[picksi1, 2014-09-02 14:50:39]

picksi@chromium.org changed reviewers:
+ picksi@chromium.org

[picksi1, 2014-09-02 14:50:40]

https://codereview.chromium.org/521613002/diff/20001/content/renderer/gpu/ren...
File content/renderer/gpu/render_widget_compositor.cc (right):

https://codereview.chromium.org/521613002/diff/20001/content/renderer/gpu/ren...
content/renderer/gpu/render_widget_compositor.cc:764: double interval_sec =
args.interval.InSecondsF();
Is base::TimeTicks() potentially slow? Should we call it once and cache the
result locally?

[Sami, 2014-09-02 14:53:30]

https://codereview.chromium.org/521613002/diff/20001/content/renderer/gpu/ren...
File content/renderer/gpu/render_widget_compositor.cc (right):

https://codereview.chromium.org/521613002/diff/20001/content/renderer/gpu/ren...
content/renderer/gpu/render_widget_compositor.cc:764: double interval_sec =
args.interval.InSecondsF();
On 2014/09/02 14:50:40, picksi1 wrote:
> Is base::TimeTicks() potentially slow? Should we call it once and cache the
> result locally?

It only constructs a TimeTicks instance that holds the value zero. To actually
get the current time you need to call base::TimeTicks::Now().

[jamesr, 2014-09-02 19:19:05]

Tests?

[Sami, 2014-09-03 13:12:37]

On 2014/09/02 19:19:05, jamesr wrote:
> Tests?

Added.

[jamesr, 2014-09-03 17:27:23]

cool, lgtm

[Sami, 2014-09-03 18:00:54]

The CQ bit was checked by skyostil@chromium.org

[commit-bot: I haz the power, 2014-09-03 18:03:11]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/skyostil@chromium.org/521613002/40001

[commit-bot: I haz the power, 2014-09-03 19:02:23]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/49669)
  android_dbg_tests_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_dbg_tes...)
  win_chromium_compile_dbg on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)
  win_chromium_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[commit-bot: I haz the power, 2014-09-03 19:25:57]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-03 19:25:57]

Try jobs failed on following builders:
  win_chromium_compile_dbg on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)

[Sami, 2014-09-04 10:56:03]

Patchset #4 (id:60001) has been deleted

[Sami, 2014-09-04 10:56:39]

The CQ bit was checked by skyostil@chromium.org

[commit-bot: I haz the power, 2014-09-04 10:57:37]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/skyostil@chromium.org/521613002/80001

[commit-bot: I haz the power, 2014-09-04 11:46:01]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-04 11:46:02]

Try jobs failed on following builders:
  android_clang_dbg_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)

[Sami, 2014-09-04 12:28:55]

The CQ bit was checked by skyostil@chromium.org

[commit-bot: I haz the power, 2014-09-04 12:30:15]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/skyostil@chromium.org/521613002/80001

[commit-bot: I haz the power, 2014-09-04 19:30:13]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-04 19:30:14]

Try jobs failed on following builders:
  win_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu_triggered...)

[Sami, 2014-09-04 22:01:14]

The CQ bit was checked by skyostil@chromium.org

[commit-bot: I haz the power, 2014-09-04 22:05:06]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/skyostil@chromium.org/521613002/80001

[commit-bot: I haz the power, 2014-09-04 22:48:42]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-04 22:48:43]

Try jobs failed on following builders:
  win_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu_triggered...)

[Sami, 2014-09-05 08:18:35]

The CQ bit was checked by skyostil@chromium.org

[commit-bot: I haz the power, 2014-09-05 08:21:24]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/skyostil@chromium.org/521613002/80001

[commit-bot: I haz the power, 2014-09-05 08:23:11]

Committed patchset #4 (id:80001) as 0d42246d8f84188e2a63339b474af521125ef76a

[commit-bot: I haz the power, 2014-09-10 03:38:00]

Patchset 4 (id:??) landed as
https://crrev.com/7759d7aef4c97d3454c15607945e23595c2dfa3e
Cr-Commit-Position: refs/heads/master@{#293476}