Reland #1: "base: Implement GetCurrentThreadPriority."

Reland #1: "base: Implement GetCurrentThreadPriority."

The Chrome thread priority is saved in the thread dictionary during
SetCurrentThreadPriority(). This seemed a better approach than using
thread_policy_get(), since there are 4 Chrome priorities which won't cleanly map
to thread flavors.

BUG=601270
Committed: https://crrev.com/23d10a36f2e815edd610098a65e5890f279d2183
Cr-Commit-Position: refs/heads/master@{#410163}

[erikchen, 2016-08-04 01:01:04]

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

[commit-bot: I haz the power, 2016-08-04 01:01:53]

Dry run: 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-08-04 02:05:44]

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

[commit-bot: I haz the power, 2016-08-04 02:05:45]

Dry run: This issue passed the CQ dry run.

[erikchen, 2016-08-05 17:17:41]

erikchen@chromium.org changed reviewers:
+ gab@chromium.org, mark@chromium.org

[erikchen, 2016-08-05 17:17:42]

mark, gab: Please review.

I reran the failed Telemetry tests locally (10.11.6) and no longer see a
regression. Let's try landing this again?

[Mark Mentovai, 2016-08-05 17:29:47]

Go for it, hope it sticks. What OS version do we run perf tests on?

[Mark Mentovai, 2016-08-05 17:30:03]

I guess the infrastructure doesn’t recognize “go for it” as LGTM.

[erikchen, 2016-08-05 20:13:11]

The CQ bit was checked by erikchen@chromium.org

[commit-bot: I haz the power, 2016-08-05 20:17:06]

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

[gab, 2016-08-05 20:34:21]

lgtm if it works, what changed though, why would it be fine now, I don't see
anything new on bug..?

[commit-bot: I haz the power, 2016-08-05 21:16:33]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-08-05 21:19:40]

Description was changed from

==========
Reland #1: "base: Implement GetCurrentThreadPriority."

The Chrome thread priority is saved in the thread dictionary during
SetCurrentThreadPriority(). This seemed a better approach than using
thread_policy_get(), since there are 4 Chrome priorities which won't cleanly map
to thread flavors.

BUG=601270
==========

to

==========
Reland #1: "base: Implement GetCurrentThreadPriority."

The Chrome thread priority is saved in the thread dictionary during
SetCurrentThreadPriority(). This seemed a better approach than using
thread_policy_get(), since there are 4 Chrome priorities which won't cleanly map
to thread flavors.

BUG=601270

Committed: https://crrev.com/23d10a36f2e815edd610098a65e5890f279d2183
Cr-Commit-Position: refs/heads/master@{#410163}
==========

[commit-bot: I haz the power, 2016-08-05 21:19:41]

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

[erikchen, 2016-08-05 21:23:53]

On 2016/08/05 20:34:21, gab wrote:
> lgtm if it works, what changed though, why would it be fine now, I don't see
> anything new on bug..?

Might have been a problem on 10.9.5. We still support that OS, but there are
much fewer users there.

[erikchen, 2016-08-08 17:11:38]

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

The reason for reverting is: Still causes startup regressions:

https://bugs.chromium.org/p/chromium/issues/detail?id=635464#c4.