DevTools: expose setLayerTreeId() so we can relate events from LayerTreeHost

DevTools: expose setLayerTreeId() so we can relate events from LayerTreeHost

Currently, we track which content layers are painted in WebCore to track layers
that belong to a page. This is a hack and does not work for non-content layers,
so let's bind layer tree to a page and updated layers to layer tree.

R=apavlov@chromium.org, jamesr@chromium.org

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=153787

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=154007

[caseq, 2013-07-01 13:37:27]

This is extracted from https://codereview.chromium.org/16878004/. We don't want
to instrument deferred canvas the way we used to do, but we still want more
reliable layer tracking.
Related chromium change: https://codereview.chromium.org/16848010

[caseq, 2013-07-03 10:25:30]

ping

[apavlov, 2013-07-03 11:48:53]

LGTM with a comment

https://codereview.chromium.org/18344005/diff/1/Source/core/inspector/Inspect...
File Source/core/inspector/InspectorTimelineAgent.h (right):

https://codereview.chromium.org/18344005/diff/1/Source/core/inspector/Inspect...
Source/core/inspector/InspectorTimelineAgent.h:124: void setLayerTreeId(int
layerTreeId) { m_layerTreeId = layerTreeId; }
Is there an issue with the fact that layerTreeId is "int" while m_layerTreeId is
"unsigned long long"?

[caseq, 2013-07-04 09:33:04]

On 2013/07/03 11:48:53, apavlov wrote:
> 
>
https://codereview.chromium.org/18344005/diff/1/Source/core/inspector/Inspect...
> Source/core/inspector/InspectorTimelineAgent.h:124: void setLayerTreeId(int
> layerTreeId) { m_layerTreeId = layerTreeId; }
> Is there an issue with the fact that layerTreeId is "int" while m_layerTreeId
is
> "unsigned long long"?

Thanks for spotting! It was harmless, but anyway it's an atavism of earlier
implementation.

[caseq, 2013-07-04 10:18:34]

+jamesr for public OWNERS. James, could you please have a look?

[jamesr, 2013-07-09 01:58:10]

lgtm

[commit-bot: I haz the power, 2013-07-09 09:05:34]

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

[commit-bot: I haz the power, 2013-07-09 09:26:26]

Sorry for I got bad news for ya.
Compile failed with a clobber build on mac_layout_rel.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_layout...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[caseq, 2013-07-09 14:35:37]

Committed patchset #1 manually as r153787 (presubmit successful).

[caseq, 2013-07-11 14:05:22]

Committed patchset #4 manually as r154007 (presubmit successful).