Use TaskScheduler instead of WorkerPool in drm_display_host_manager.cc.

Use TaskScheduler instead of WorkerPool in drm_display_host_manager.cc.

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

May Block:
  Tasks posted with MayBlock() may block. This includes but is not
  limited to tasks that wait on synchronous file I/O operations:
  read or write a file from disk, interact with a pipe or a socket,
  rename or delete a file, enumerate files in a directory, etc. This
  trait isn't required for the mere use of locks.

BUG=659191
Committed: https://crrev.com/f817d9ad97999d190dc84ec6b170c3224f20f6cd
Cr-Commit-Position: refs/heads/master@{#441141}

[fdoray, 2017-01-01 19:52:40]

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

[commit-bot: I haz the power, 2017-01-01 19:52:45]

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, 2017-01-01 20:20:57]

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

[commit-bot: I haz the power, 2017-01-01 20:20:58]

Dry run: This issue passed the CQ dry run.

[fdoray, 2017-01-01 23:17:12]

fdoray@chromium.org changed reviewers:
+ dnicoara@chromium.org

[fdoray, 2017-01-01 23:17:13]

PTAL. WorkerPool is being deprecated in favor of TaskScheduler.

[dnicoara, 2017-01-03 15:50:56]

lgtm

[fdoray, 2017-01-03 16:44:38]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-01-03 16:44:48]

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-01-03 17:09:20]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1483461878506630, "parent_rev":
"694bf8a89fd6d85890355454c8736bcb27a5317f", "commit_rev":
"4238abfe3d8d2ca14ed29fed2946336b9b85dae9"}

[commit-bot: I haz the power, 2017-01-03 17:09:48]

Description was changed from

==========
Use TaskScheduler instead of WorkerPool in drm_display_host_manager.cc.

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

May Block:
  Tasks posted with MayBlock() may block. This includes but is not
  limited to tasks that wait on synchronous file I/O operations:
  read or write a file from disk, interact with a pipe or a socket,
  rename or delete a file, enumerate files in a directory, etc. This
  trait isn't required for the mere use of locks.

BUG=659191
==========

to

==========
Use TaskScheduler instead of WorkerPool in drm_display_host_manager.cc.

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

May Block:
  Tasks posted with MayBlock() may block. This includes but is not
  limited to tasks that wait on synchronous file I/O operations:
  read or write a file from disk, interact with a pipe or a socket,
  rename or delete a file, enumerate files in a directory, etc. This
  trait isn't required for the mere use of locks.

BUG=659191

Review-Url: https://codereview.chromium.org/2603153003
==========

[commit-bot: I haz the power, 2017-01-03 17:09:49]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2017-01-03 17:13:17]

Description was changed from

==========
Use TaskScheduler instead of WorkerPool in drm_display_host_manager.cc.

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

May Block:
  Tasks posted with MayBlock() may block. This includes but is not
  limited to tasks that wait on synchronous file I/O operations:
  read or write a file from disk, interact with a pipe or a socket,
  rename or delete a file, enumerate files in a directory, etc. This
  trait isn't required for the mere use of locks.

BUG=659191

Review-Url: https://codereview.chromium.org/2603153003
==========

to

==========
Use TaskScheduler instead of WorkerPool in drm_display_host_manager.cc.

The following traits are used:

Priority: Inherited (default)
  The priority is inherited from the calling context (i.e. TaskTraits
  are initialized with the priority of the current task).

Shutdown behavior: CONTINUE_ON_SHUTDOWN
  Tasks posted with this mode which have not started executing before
  shutdown is initiated will never run. Tasks with this mode running at
  shutdown will be ignored (the worker will not be joined).

  Note: Tasks that were previously posted to base::WorkerPool should
  use this shutdown behavior because this is how base::WorkerPool
  handles all its tasks.

May Block:
  Tasks posted with MayBlock() may block. This includes but is not
  limited to tasks that wait on synchronous file I/O operations:
  read or write a file from disk, interact with a pipe or a socket,
  rename or delete a file, enumerate files in a directory, etc. This
  trait isn't required for the mere use of locks.

BUG=659191

Committed: https://crrev.com/f817d9ad97999d190dc84ec6b170c3224f20f6cd
Cr-Commit-Position: refs/heads/master@{#441141}
==========

[commit-bot: I haz the power, 2017-01-03 17:13:18]

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