android: Add the target to toplevel Looper events in tracing,

android: Add the target to toplevel Looper events in tracing.

When tracing is enabled, toplevel Looper tasks come from Chrome and the
system. Non-native tasks are a black box, as they only show up as
"toplevel.dispatchMessage" in tracing. This commit adds the "target" of
the looper task as a parameter in the trace.

For instance (from a startup trace):
- android.view.ViewRootImpl$ViewRootHandler
- android.view.Choreographer$FrameHandler
- android.os.AsyncTask$InternalHandler
- com.google.android.gms.common.internal.s

This allows to distinguish between framework time, Chrome's Java tasks
and third-party libs (GMSCore above).

About performance cost:
- The Java string is already created by the framework code, we extract a
  substring of it.
- A new parameter for each toplevel trace event.

Review-Url: https://codereview.chromium.org/2883993002
Cr-Commit-Position: refs/heads/master@{#472043}
Committed: https://chromium.googlesource.com/chromium/src/+/71be2dc15e6765170cbc0054bb12fec403b9bed3

[Benoit L, 2017-05-15 16:00:57]

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

[commit-bot: I haz the power, 2017-05-15 16:01:53]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Benoit L, 2017-05-15 16:01:58]

Description was changed from

==========
android: Add the target to toplevel Looper events in tracing,

When tracing is enabled, toplevel Looper tasks come from Chrome and the
system. Non-native tasks are a black box, as they only show up as
"toplevel.dispatchMessage" in tracing. This commit adds the "target" of
the looper task as a parameter in the trace.

For instance (from a startup trace):
- android.view.ViewRootImpl$ViewRootHandler
- android.view.Choreographer$FrameHandler
- android.os.AsyncTask$InternalHandler
- com.google.android.gms.common.internal.s

This allows to distinguish between framework time, Chrome's Java tasks
and third-party libs (GMSCore above).

About performance cost:
- The Java string is already created by the framework code, we extract a
  substring of it.
- A new parameter for each toplevel trace event.
==========

to

==========
android: Add the target to toplevel Looper events in tracing.

When tracing is enabled, toplevel Looper tasks come from Chrome and the
system. Non-native tasks are a black box, as they only show up as
"toplevel.dispatchMessage" in tracing. This commit adds the "target" of
the looper task as a parameter in the trace.

For instance (from a startup trace):
- android.view.ViewRootImpl$ViewRootHandler
- android.view.Choreographer$FrameHandler
- android.os.AsyncTask$InternalHandler
- com.google.android.gms.common.internal.s

This allows to distinguish between framework time, Chrome's Java tasks
and third-party libs (GMSCore above).

About performance cost:
- The Java string is already created by the framework code, we extract a
  substring of it.
- A new parameter for each toplevel trace event.
==========

[Benoit L, 2017-05-15 16:02:51]

lizeb@chromium.org changed reviewers:
+ agrieve@chromium.org

[commit-bot: I haz the power, 2017-05-15 17:00:32]

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

[commit-bot: I haz the power, 2017-05-15 17:00:32]

Dry run: This issue passed the CQ dry run.

[agrieve, 2017-05-15 17:55:36]

love it! lgtm

[Benoit L, 2017-05-16 08:30:11]

The CQ bit was checked by lizeb@chromium.org

[commit-bot: I haz the power, 2017-05-16 08:30:26]

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-05-16 08:35:58]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494923411213730, "parent_rev":
"5bd5c34ac5884eb5e3bf9a613ad0b51dee2c394b", "commit_rev":
"71be2dc15e6765170cbc0054bb12fec403b9bed3"}

[commit-bot: I haz the power, 2017-05-16 08:36:08]

Description was changed from

==========
android: Add the target to toplevel Looper events in tracing.

When tracing is enabled, toplevel Looper tasks come from Chrome and the
system. Non-native tasks are a black box, as they only show up as
"toplevel.dispatchMessage" in tracing. This commit adds the "target" of
the looper task as a parameter in the trace.

For instance (from a startup trace):
- android.view.ViewRootImpl$ViewRootHandler
- android.view.Choreographer$FrameHandler
- android.os.AsyncTask$InternalHandler
- com.google.android.gms.common.internal.s

This allows to distinguish between framework time, Chrome's Java tasks
and third-party libs (GMSCore above).

About performance cost:
- The Java string is already created by the framework code, we extract a
  substring of it.
- A new parameter for each toplevel trace event.
==========

to

==========
android: Add the target to toplevel Looper events in tracing.

When tracing is enabled, toplevel Looper tasks come from Chrome and the
system. Non-native tasks are a black box, as they only show up as
"toplevel.dispatchMessage" in tracing. This commit adds the "target" of
the looper task as a parameter in the trace.

For instance (from a startup trace):
- android.view.ViewRootImpl$ViewRootHandler
- android.view.Choreographer$FrameHandler
- android.os.AsyncTask$InternalHandler
- com.google.android.gms.common.internal.s

This allows to distinguish between framework time, Chrome's Java tasks
and third-party libs (GMSCore above).

About performance cost:
- The Java string is already created by the framework code, we extract a
  substring of it.
- A new parameter for each toplevel trace event.

Review-Url: https://codereview.chromium.org/2883993002
Cr-Commit-Position: refs/heads/master@{#472043}
Committed:
https://chromium.googlesource.com/chromium/src/+/71be2dc15e6765170cbc0054bb12...
==========

[commit-bot: I haz the power, 2017-05-16 08:36:09]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/71be2dc15e6765170cbc0054bb12...