Plumbing input event latency reporting through Mus GPU.

Plumbing input event latency reporting through Mus GPU.

This CL mostly shuffles things around to enable input event latency reporting
in Mus. However there are two functional changes:
- DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT (which replaces
  INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT) is logged if there
  are ANY latency components present.
- OnGpuSwapBuffersCompleted() is now called if there are ANY latency components
  present. 
This shouldn't have any effect on the browser UMA latency reporting, because
currently OnGpuSwapBuffersCompleted() exits early if it doesn't see
blink-specific latency components. However it should prove useful for getting
latency data for non-blink use cases in the future.

Other changes:
- Adds logging of DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT in
  SurfaceFactory::SubmitCompositorFrame().
- Plumbs through LatencyInfo propagation for the in-process GPU
  command buffer case (i.e. for Mus GPU).
- Factors out OnGpuSwapBuffersCompleted() from RenderWidgetHostLatencyTracker
  into LatencyTracker - a new class in ui/latency, which RWHLatencyTracker now
  extends.
- Adds LatencyTracker to DisplayOutputSurface, and calls
  LatencyTracker::OnGpuSwapBuffersCompleted from
  DisplayOutputSurface::OnGpuSwapBuffersCompleted, which ensures UMA latency
  data is reported in Mus.

BUG=686865
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

[mfomitchev, 2017-04-06 21:20:03]

Description was changed from

==========
Plumbing input event latency reporting through Mus GPU.

The CL mostly shuffles things around to make sure input event latency is
reported in Mus. However there are two significant changes:


- Renames INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT to
  DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT, and adds logging of this
  component in SurfaceFactory::SubmitCompositorFrame.
- Adds logging of GPU latency components in
- Plumbs through LatencyInfo propagation for the in-process GPU
  command buffer case (i.e. for Mus GPU).
- Factors out OnGpuSwapBuffersCompleted() from RenderWidgetHostLatencyTracker
  into LatencyTracker - a new class in ui/latency, which RWHLatencyTracker now
  extends
- Adds LatencyTracker to DisplayOutputSurface, and calls
  LatencyTracker::OnGpuSwapBuffersCompleted from
  DisplayOutputSurface::OnGpuSwapBuffersCompleted, which ensures latency is
  reported in Mus.

BUG=686865
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Plumbing input event latency reporting through Mus GPU.

This CL mostly shuffles things around to enable input event latency reporting
in Mus. However there are two functional changes:
- DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT (which replaces
  INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT) is logged if there
  are ANY latency components present.
- OnGpuSwapBuffersCompleted() is now called if there are ANY latency components
  present. 

- Renames INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT to
  DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT, and adds logging of this
  component in SurfaceFactory::SubmitCompositorFrame.
- Adds logging of GPU latency components in
- Plumbs through LatencyInfo propagation for the in-process GPU
  command buffer case (i.e. for Mus GPU).
- Factors out OnGpuSwapBuffersCompleted() from RenderWidgetHostLatencyTracker
  into LatencyTracker - a new class in ui/latency, which RWHLatencyTracker now
  extends
- Adds LatencyTracker to DisplayOutputSurface, and calls
  LatencyTracker::OnGpuSwapBuffersCompleted from
  DisplayOutputSurface::OnGpuSwapBuffersCompleted, which ensures latency is
  reported in Mus.

BUG=686865
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[mfomitchev, 2017-04-06 21:31:12]

Description was changed from

==========
Plumbing input event latency reporting through Mus GPU.

This CL mostly shuffles things around to enable input event latency reporting
in Mus. However there are two functional changes:
- DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT (which replaces
  INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT) is logged if there
  are ANY latency components present.
- OnGpuSwapBuffersCompleted() is now called if there are ANY latency components
  present. 

- Renames INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT to
  DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT, and adds logging of this
  component in SurfaceFactory::SubmitCompositorFrame.
- Adds logging of GPU latency components in
- Plumbs through LatencyInfo propagation for the in-process GPU
  command buffer case (i.e. for Mus GPU).
- Factors out OnGpuSwapBuffersCompleted() from RenderWidgetHostLatencyTracker
  into LatencyTracker - a new class in ui/latency, which RWHLatencyTracker now
  extends
- Adds LatencyTracker to DisplayOutputSurface, and calls
  LatencyTracker::OnGpuSwapBuffersCompleted from
  DisplayOutputSurface::OnGpuSwapBuffersCompleted, which ensures latency is
  reported in Mus.

BUG=686865
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Plumbing input event latency reporting through Mus GPU.

This CL mostly shuffles things around to enable input event latency reporting
in Mus. However there are two functional changes:
- DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT (which replaces
  INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT) is logged if there
  are ANY latency components present.
- OnGpuSwapBuffersCompleted() is now called if there are ANY latency components
  present. 
This shouldn't have any effect on the browser UMA latency reporting, because
currently OnGpuSwapBuffersCompleted() exits early if it doesn't see
blink-specific latency components. However it should prove useful for getting
latency data for non-blink use cases in the future.

Other changes:
- Adds logging of DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT in
  SurfaceFactory::SubmitCompositorFrame().
- Plumbs through LatencyInfo propagation for the in-process GPU
  command buffer case (i.e. for Mus GPU).
- Factors out OnGpuSwapBuffersCompleted() from RenderWidgetHostLatencyTracker
  into LatencyTracker - a new class in ui/latency, which RWHLatencyTracker now
  extends.
- Adds LatencyTracker to DisplayOutputSurface, and calls
  LatencyTracker::OnGpuSwapBuffersCompleted from
  DisplayOutputSurface::OnGpuSwapBuffersCompleted, which ensures UMA latency
  data is reported in Mus.

BUG=686865
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[mfomitchev, 2017-04-06 21:34:13]

Description was changed from

==========
Plumbing input event latency reporting through Mus GPU.

This CL mostly shuffles things around to enable input event latency reporting
in Mus. However there are two functional changes:
- DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT (which replaces
  INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT) is logged if there
  are ANY latency components present.
- OnGpuSwapBuffersCompleted() is now called if there are ANY latency components
  present. 
This shouldn't have any effect on the browser UMA latency reporting, because
currently OnGpuSwapBuffersCompleted() exits early if it doesn't see
blink-specific latency components. However it should prove useful for getting
latency data for non-blink use cases in the future.

Other changes:
- Adds logging of DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT in
  SurfaceFactory::SubmitCompositorFrame().
- Plumbs through LatencyInfo propagation for the in-process GPU
  command buffer case (i.e. for Mus GPU).
- Factors out OnGpuSwapBuffersCompleted() from RenderWidgetHostLatencyTracker
  into LatencyTracker - a new class in ui/latency, which RWHLatencyTracker now
  extends.
- Adds LatencyTracker to DisplayOutputSurface, and calls
  LatencyTracker::OnGpuSwapBuffersCompleted from
  DisplayOutputSurface::OnGpuSwapBuffersCompleted, which ensures UMA latency
  data is reported in Mus.

BUG=686865
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Plumbing input event latency reporting through Mus GPU.

This CL mostly shuffles things around to enable input event latency reporting
in Mus. However there are two functional changes:
- DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT (which replaces
  INPUT_EVENT_BROWSER_RECEIVED_RENDERER_SWAP_COMPONENT) is logged if there
  are ANY latency components present.
- OnGpuSwapBuffersCompleted() is now called if there are ANY latency components
  present. 
This shouldn't have any effect on the browser UMA latency reporting, because
currently OnGpuSwapBuffersCompleted() exits early if it doesn't see
blink-specific latency components. However it should prove useful for getting
latency data for non-blink use cases in the future.

Other changes:
- Adds logging of DISPLAY_COMPOSITOR_RECEIVED_FRAME_COMPONENT in
  SurfaceFactory::SubmitCompositorFrame().
- Plumbs through LatencyInfo propagation for the in-process GPU
  command buffer case (i.e. for Mus GPU).
- Factors out OnGpuSwapBuffersCompleted() from RenderWidgetHostLatencyTracker
  into LatencyTracker - a new class in ui/latency, which RWHLatencyTracker now
  extends.
- Adds LatencyTracker to DisplayOutputSurface, and calls
  LatencyTracker::OnGpuSwapBuffersCompleted from
  DisplayOutputSurface::OnGpuSwapBuffersCompleted, which ensures UMA latency
  data is reported in Mus.

BUG=686865
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[mfomitchev, 2017-04-06 21:49:41]

The CQ bit was checked by mfomitchev@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-06 21:51:08]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-06 22:44:24]

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

[commit-bot: I haz the power, 2017-04-06 22:44:25]

Dry run: Try jobs failed on following builders:
  win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)

[mfomitchev, 2017-04-07 18:46:33]

The CQ bit was checked by mfomitchev@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-07 18:47:13]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[mfomitchev, 2017-04-07 18:53:54]

The CQ bit was checked by mfomitchev@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-07 18:54:32]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-07 20:18:01]

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

[commit-bot: I haz the power, 2017-04-07 20:18:02]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[mfomitchev, 2017-04-07 22:05:41]

The CQ bit was checked by mfomitchev@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-07 22:06:16]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[mfomitchev, 2017-04-07 22:09:05]

mfomitchev@chromium.org changed reviewers:
+ sadrul@chromium.org, tdresser@chromium.org

[mfomitchev, 2017-04-07 22:09:06]

tdresser@chromium.org: Please review changes in 
ui/latency and latency tracker changes in content/

sadrul@chromium.org: 
Mostly looking for feedback on the "functional changes" highlighted in the CL
description - does the approach make sense to you?

[commit-bot: I haz the power, 2017-04-07 23:14:51]

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

[commit-bot: I haz the power, 2017-04-07 23:14:52]

Dry run: This issue passed the CQ dry run.

[tdresser, 2017-04-10 14:39:48]

Could we split the functional changes into a separate patch?

[mfomitchev, 2017-04-10 14:48:53]

On 2017/04/10 14:39:48, tdresser wrote:
> Could we split the functional changes into a separate patch?

Sorry, my CL description was pretty confusing. The functional changes I am
referring to are for the difference between the Mus flow and the "classic
chrome" flow. This CL does not change the "classic chrome" flow, and the Mus
flow (post renderer) wasn't implemented before. It is worth noting that the Mus
flow will become the default once Mus ships (which hopefully happens next
quarter).

I will update the CL description to make it less confusing.

[mfomitchev, 2017-04-10 14:59:52]

Following an offline discussion - will move RWHLatencyTracker split into a
separate patch. Stay tuned.

[mfomitchev, 2017-04-10 19:46:23]

https://codereview.chromium.org/2814483002/ and
https://codereview.chromium.org/2806163004/ are the two CLs.
Sadrul - I haven't added you as the reviewer, since most non-trivial changes are
covered by Tim, but please feel free to do a drive by if you feel like it.