Revert of Reland #1: "base: Implement GetCurrentThreadPriority."

Revert of Reland #1: "base: Implement GetCurrentThreadPriority." (patchset #2 id:20001 of https://codereview.chromium.org/2215513002/ )

Reason for revert:
Still causes startup regressions:

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

Original issue's description:
> 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}

TBR=mark@chromium.org,gab@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=601270
Committed: https://crrev.com/23c669b5b4cf228dab6da2cc47293b4650a7b923
Cr-Commit-Position: refs/heads/master@{#410390}

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

The CQ bit was checked by erikchen@chromium.org

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

Created Revert of Reland #1: "base: Implement GetCurrentThreadPriority."

[commit-bot: I haz the power, 2016-08-08 17:12:00]

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-08 17:52:59]

Description was changed from

==========
Revert of Reland #1: "base: Implement GetCurrentThreadPriority." (patchset #2
id:20001 of https://codereview.chromium.org/2215513002/ )

Reason for revert:
Still causes startup regressions:

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

Original issue's description:
> 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}

TBR=mark@chromium.org,gab@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=601270
==========

to

==========
Revert of Reland #1: "base: Implement GetCurrentThreadPriority." (patchset #2
id:20001 of https://codereview.chromium.org/2215513002/ )

Reason for revert:
Still causes startup regressions:

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

Original issue's description:
> 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}

TBR=mark@chromium.org,gab@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=601270
==========

[commit-bot: I haz the power, 2016-08-08 17:53:00]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-08 17:56:12]

Description was changed from

==========
Revert of Reland #1: "base: Implement GetCurrentThreadPriority." (patchset #2
id:20001 of https://codereview.chromium.org/2215513002/ )

Reason for revert:
Still causes startup regressions:

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

Original issue's description:
> 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}

TBR=mark@chromium.org,gab@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=601270
==========

to

==========
Revert of Reland #1: "base: Implement GetCurrentThreadPriority." (patchset #2
id:20001 of https://codereview.chromium.org/2215513002/ )

Reason for revert:
Still causes startup regressions:

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

Original issue's description:
> 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}

TBR=mark@chromium.org,gab@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=601270

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

[commit-bot: I haz the power, 2016-08-08 17:56:13]

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