Introduce PREPARE_FOR_EXECUTION_WITH_CONTEXT_IN_RUNTIME_CALL_STATS_SCOPE

Introduce PREPARE_FOR_EXECUTION_WITH_CONTEXT_IN_RUNTIME_CALL_STATS_SCOPE

Previously, macro like PREPARE_FOR_EXECUTION_WITH_CALLBACK will end up calling
LOG_API, where we create a runtime call timer scope when we enable tracing with
runtime call stats, however since the flag will be enabled after calling
TRACE_EVENT_CALL_STATS_SCOPED, this will end up with incorrect timestamp. Thus,
we introduce a new macro
PREPARE_FOR_EXECUTION_WITH_CONTEXT_IN_RUNTIME_CALL_STATS_SCOPE, which will call
TRACE_EVENT_CALL_STATS_SCOPED inside it.

BUG=v8:5089
Committed: https://crrev.com/9df94139d8e240762e9bc9f29b86648ae78f7627
Cr-Commit-Position: refs/heads/master@{#39458}

[lpy, 2016-09-15 22:58:46]

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

[commit-bot: I haz the power, 2016-09-15 22:58:54]

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

[lpy, 2016-09-15 23:02:52]

lpy@chromium.org changed reviewers:
+ cbruni@chromium.org, fmeawad@chromium.org

[lpy, 2016-09-15 23:02:53]

PTAL.

We are using `isolate` when we create a tracing scope for runtime call stats,
but the isolate is created in PREPARE_FOR_EXECUTION_WITH_CONTEXT, so I think the
fix should be add the same macro but with runtime call stats scope in it.

[lpy, 2016-09-15 23:08:59]

The timestamp is now reasonable, please take a look at this screen shot.
(chromium.org domain)

This was tested on chrome TOT.

https://drive.google.com/a/chromium.org/file/d/0B0DRpwuGZfeGTGJQeDhycm1BbVU/v...

[commit-bot: I haz the power, 2016-09-15 23:25:57]

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

[commit-bot: I haz the power, 2016-09-15 23:25:58]

Dry run: This issue passed the CQ dry run.

[Camillo Bruni, 2016-09-15 23:42:05]

lgtm

[fmeawad, 2016-09-15 23:47:57]

lgtm

[lpy, 2016-09-16 00:09:12]

The CQ bit was checked by lpy@chromium.org

[commit-bot: I haz the power, 2016-09-16 00:09:18]

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, 2016-09-16 00:11:20]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-16 00:11:43]

Description was changed from

==========
Introduce PREPARE_FOR_EXECUTION_WITH_CONTEXT_IN_RUNTIME_CALL_STATS_SCOPE

Previously, macro like PREPARE_FOR_EXECUTION_WITH_CALLBACK will end up calling
LOG_API, where we create a runtime call timer scope when we enable tracing with
runtime call stats, however since the flag will be enabled after calling
TRACE_EVENT_CALL_STATS_SCOPED, this will end up with incorrect timestamp. Thus,
we introduce a new macro
PREPARE_FOR_EXECUTION_WITH_CONTEXT_IN_RUNTIME_CALL_STATS_SCOPE, which will call
TRACE_EVENT_CALL_STATS_SCOPED inside it.

BUG=v8:5089
==========

to

==========
Introduce PREPARE_FOR_EXECUTION_WITH_CONTEXT_IN_RUNTIME_CALL_STATS_SCOPE

Previously, macro like PREPARE_FOR_EXECUTION_WITH_CALLBACK will end up calling
LOG_API, where we create a runtime call timer scope when we enable tracing with
runtime call stats, however since the flag will be enabled after calling
TRACE_EVENT_CALL_STATS_SCOPED, this will end up with incorrect timestamp. Thus,
we introduce a new macro
PREPARE_FOR_EXECUTION_WITH_CONTEXT_IN_RUNTIME_CALL_STATS_SCOPE, which will call
TRACE_EVENT_CALL_STATS_SCOPED inside it.

BUG=v8:5089

Committed: https://crrev.com/9df94139d8e240762e9bc9f29b86648ae78f7627
Cr-Commit-Position: refs/heads/master@{#39458}
==========

[commit-bot: I haz the power, 2016-09-16 00:11:44]

Patchset 1 (id:??) landed as
https://crrev.com/9df94139d8e240762e9bc9f29b86648ae78f7627
Cr-Commit-Position: refs/heads/master@{#39458}