cc:: Add LatencyQuery logic back into OutputSurface.

cc:: Add LatencyQuery logic back into OutputSurface.

Flickering no longer evident on Note 3 Device.

BUG=317928
Committed: https://crrev.com/64579af21919e40dc017eee463a0f5cd53976ad1
Cr-Commit-Position: refs/heads/master@{#294292}

[orglofch, 2014-09-10 20:01:26]

Patchset #2 (id:20001) has been deleted

[orglofch, 2014-09-10 20:41:51]

orglofch@chromium.org changed reviewers:
+ brianderson@chromium.org

[brianderson, 2014-09-10 22:36:35]

https://codereview.chromium.org/560123002/diff/1/cc/output/output_surface.cc
File cc/output/output_surface.cc (right):

https://codereview.chromium.org/560123002/diff/1/cc/output/output_surface.cc#...
cc/output/output_surface.cc:38: const double kGpuLatencyEstimationPercentile =
100.0;
In other cases where we record history, we've seen that taking the worst case
isn't ideal.

Let's change the percentile to be 90 as our starting point this time.

https://codereview.chromium.org/560123002/diff/1/cc/output/output_surface.cc#...
cc/output/output_surface.cc:288: while (pending_gpu_latency_query_ids_.size()) {
Can you add a comment indicating this loop collects completed latency queries.

https://codereview.chromium.org/560123002/diff/1/cc/output/output_surface.cc#...
cc/output/output_surface.cc:329: unsigned gpu_latency_query_id;
A comment would hlep here too.

https://codereview.chromium.org/560123002/diff/1/cc/output/output_surface.cc#...
cc/output/output_surface.cc:337:
context_provider_->ContextGL()->BeginQueryEXT(GL_LATENCY_QUERY_CHROMIUM,
And here.

[brianderson, 2014-09-10 22:56:53]

lgtm!

[orglofch, 2014-09-10 23:16:28]

The CQ bit was checked by orglofch@chromium.org

[orglofch, 2014-09-10 23:16:29]

The CQ bit was unchecked by orglofch@chromium.org

[orglofch, 2014-09-11 00:14:11]

The CQ bit was checked by orglofch@chromium.org

[commit-bot: I haz the power, 2014-09-11 00:17:20]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/560123002/40001

[commit-bot: I haz the power, 2014-09-11 01:57:23]

Committed patchset #2 (id:40001) as 40497523d46a5316fa5d704d2ccd615d26702722

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

Patchset 2 (id:??) landed as
https://crrev.com/64579af21919e40dc017eee463a0f5cd53976ad1
Cr-Commit-Position: refs/heads/master@{#294292}

[orglofch, 2014-09-12 21:48:05]

A revert of this CL (patchset #3 id:60001) has been created in
https://codereview.chromium.org/564203002/ by orglofch@chromium.org.

The reason for reverting is: Accidental commit on same branch.

[orglofch, 2014-09-12 21:49:38]

Patchset #3 (id:60001) has been deleted

[orglofch, 2014-09-18 19:08:24]

A revert of this CL (patchset #2 id:40001) has been created in
https://codereview.chromium.org/580123003/ by orglofch@chromium.org.

The reason for reverting is: Redundancy in additional query mechanism, will
modify to work using latency_info..