cc: add more devtools instrumentation

cc: add more devtools instrumentation

This adds didRequestMainThreadFrame() and didDrawFrame() so we can better
track impl-side frame lifecycle in DevTools

R=danakj, nduca

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=251127

[caseq, 2014-02-11 17:27:51]

Dana & Nat, please take a look. This is mostly along the lines of the existing
devtools_instrumentation. We need these two as we'd like to expose only the
frames that were actually drawing something and we'd like to hide the impl-side
frames that happen while the commit is pending to simplify frame overview in
DevTools.

[danakj, 2014-02-11 17:58:13]

Looks OK to me with a style question. *Tosses to Nat*

https://codereview.chromium.org/144463016/diff/1/cc/debug/devtools_instrument...
File cc/debug/devtools_instrumentation.h (right):

https://codereview.chromium.org/144463016/diff/1/cc/debug/devtools_instrument...
cc/debug/devtools_instrumentation.h:106: inline void didDrawFrame(int
layer_tree_host_id) {
why do functions in this file have webkit style names?

[caseq, 2014-02-11 18:16:28]

On 2014/02/11 17:58:13, danakj wrote:

>
https://codereview.chromium.org/144463016/diff/1/cc/debug/devtools_instrument...
> cc/debug/devtools_instrumentation.h:106: inline void didDrawFrame(int
> layer_tree_host_id) {
> why do functions in this file have webkit style names?

Ah, sorry, there's no justification for that expect for my finger memory :( I'll
capitalize the first letter on all of them.

[nduca, 2014-02-12 18:56:43]

lgtm

[caseq, 2014-02-13 16:30:18]

The CQ bit was checked by caseq@chromium.org

[commit-bot: I haz the power, 2014-02-13 16:30:43]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/caseq@chromium.org/144463016/60001

[commit-bot: I haz the power, 2014-02-13 19:48:03]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/caseq@chromium.org/144463016/60001

[commit-bot: I haz the power, 2014-02-13 21:28:38]

Change committed as 251127