gpu: Replace GpuMsg_CollectGraphicsInfo with mojom API.

gpu: Replace GpuMsg_CollectGraphicsInfo with mojom API.

This introduces mojom.GpuService.RequestCompleteGpuInfo() API to replace
the GpuMsg_CollectGraphicsInfo chrome ipc message.

BUG=643746
Review-Url: https://codereview.chromium.org/2753293003
Cr-Commit-Position: refs/heads/master@{#459632}
Committed: https://chromium.googlesource.com/chromium/src/+/9e029acf8a371e301aefcb51b4863137adccde68

[sadrul, 2017-03-17 20:52:38]

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

[commit-bot: I haz the power, 2017-03-17 20:53:23]

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-03-17 22:29:43]

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

[commit-bot: I haz the power, 2017-03-17 22:29:44]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[sadrul, 2017-03-18 00:24:57]

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

[commit-bot: I haz the power, 2017-03-18 00:25:50]

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-03-18 00:56:57]

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

[commit-bot: I haz the power, 2017-03-18 00:56:58]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[sadrul, 2017-03-18 01:11:28]

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

[commit-bot: I haz the power, 2017-03-18 01:12:00]

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-03-18 03:56:37]

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

[commit-bot: I haz the power, 2017-03-18 03:56:37]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[sadrul, 2017-03-19 23:44:50]

Description was changed from

==========
gpu: Replace GpuMsg_CollectGraphicsInfo with mojom API.

...

BUG=...
==========

to

==========
gpu: Replace GpuMsg_CollectGraphicsInfo with mojom API.

This introduces mojom.GpuService.RequestCompleteGpuInfo() API to replace
the GpuMsg_CollectGraphicsInfo chrome ipc message. This makes a subtle
change in how the response is handled: the response in the browser used
to be handled in the UI thread, but with this change, the response is
handled in the IO thread. However, the callback for the response notifies
the GpuDataManagerImpl instance, which can be accessed from both the IO
and UI threads. So this change should not affect the actual behaviour.

BUG=643746
==========

[sadrul, 2017-03-20 00:00:13]

sadrul@chromium.org changed reviewers:
+ piman@chromium.org, tsepez@chromium.org

[sadrul, 2017-03-20 00:00:14]

tsepez@ for mojom and messages change.

piman@ for all of it.

Thanks!

[sadrul, 2017-03-20 05:11:22]

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

[commit-bot: I haz the power, 2017-03-20 05:11:36]

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-03-20 06:20:55]

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

[commit-bot: I haz the power, 2017-03-20 06:20:56]

Dry run: This issue passed the CQ dry run.

[Tom Sepez, 2017-03-20 17:20:44]

Messages/Mojom LGTM (equivalent functionality).

[piman, 2017-03-20 21:02:36]

https://codereview.chromium.org/2753293003/diff/50001/content/browser/gpu/gpu...
File content/browser/gpu/gpu_data_manager_impl_private.cc (right):

https://codereview.chromium.org/2753293003/diff/50001/content/browser/gpu/gpu...
content/browser/gpu/gpu_data_manager_impl_private.cc:433:
GpuDataManagerImpl::GetInstance()->UpdateGpuInfo(gpu_info);
Should we hop back to the UI thread, though?
I know there's a lock around accesses to GpuDataManagerImplPrivate, but 
GpuDataManagerImplPrivate::UpdateGpuInfo calls back into things (e.g. 
GetContentClient()->SetGpuInfo ) which I'm not sure is safe to do from the IO
thread.

[sadrul, 2017-03-20 21:18:26]

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

[commit-bot: I haz the power, 2017-03-20 21:19:08]

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

[sadrul, 2017-03-20 21:21:44]

https://codereview.chromium.org/2753293003/diff/50001/content/browser/gpu/gpu...
File content/browser/gpu/gpu_data_manager_impl_private.cc (right):

https://codereview.chromium.org/2753293003/diff/50001/content/browser/gpu/gpu...
content/browser/gpu/gpu_data_manager_impl_private.cc:433:
GpuDataManagerImpl::GetInstance()->UpdateGpuInfo(gpu_info);
On 2017/03/20 21:02:36, piman wrote:
> Should we hop back to the UI thread, though?
> I know there's a lock around accesses to GpuDataManagerImplPrivate, but 
> GpuDataManagerImplPrivate::UpdateGpuInfo calls back into things (e.g. 
> GetContentClient()->SetGpuInfo ) which I'm not sure is safe to do from the IO
> thread.

Ah, that's a good point! I have moved this to hop onto the UI thread before
updating GPUInfo.

Would it make sense to add some DCHECKs into GpuDataManager[Impl[Private]] to
make sure such functions are called from the right thread (where applicable) to
avoid accidental regressions?

[piman, 2017-03-20 21:33:54]

https://codereview.chromium.org/2753293003/diff/50001/content/browser/gpu/gpu...
File content/browser/gpu/gpu_data_manager_impl_private.cc (right):

https://codereview.chromium.org/2753293003/diff/50001/content/browser/gpu/gpu...
content/browser/gpu/gpu_data_manager_impl_private.cc:433:
GpuDataManagerImpl::GetInstance()->UpdateGpuInfo(gpu_info);
On 2017/03/20 21:21:44, sadrul wrote:
> On 2017/03/20 21:02:36, piman wrote:
> > Should we hop back to the UI thread, though?
> > I know there's a lock around accesses to GpuDataManagerImplPrivate, but 
> > GpuDataManagerImplPrivate::UpdateGpuInfo calls back into things (e.g. 
> > GetContentClient()->SetGpuInfo ) which I'm not sure is safe to do from the
IO
> > thread.
> 
> Ah, that's a good point! I have moved this to hop onto the UI thread before
> updating GPUInfo.
> 
> Would it make sense to add some DCHECKs into GpuDataManager[Impl[Private]] to
> make sure such functions are called from the right thread (where applicable)
to
> avoid accidental regressions?

I think it would be useful. GpuDataManagerImplPrivate is a bit of a mess and not
necessarily well behaved everywhere. It "looks" thread-safe for the most part,
but I think it's not in several places (UpdateGpuInfo being one).

[piman, 2017-03-20 21:33:59]

lgtm

[sadrul, 2017-03-20 22:48:29]

The CQ bit was checked by sadrul@chromium.org

[sadrul, 2017-03-20 22:48:29]

The patchset sent to the CQ was uploaded after l-g-t-m from tsepez@chromium.org
Link to the patchset: https://codereview.chromium.org/2753293003/#ps70001
(title: "Run callback on UI thread. Tot merge.")

[commit-bot: I haz the power, 2017-03-20 22:48:50]

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-03-21 00:01:25]

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

[commit-bot: I haz the power, 2017-03-21 00:01:26]

Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[sadrul, 2017-03-21 02:12:41]

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

[commit-bot: I haz the power, 2017-03-21 02:13:12]

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-03-21 04:39:37]

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

[commit-bot: I haz the power, 2017-03-21 04:39:38]

Dry run: Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[sadrul, 2017-03-21 06:41:27]

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

[commit-bot: I haz the power, 2017-03-21 06:41:38]

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-03-21 08:47:25]

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

[commit-bot: I haz the power, 2017-03-21 08:47:26]

Dry run: Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[sadrul, 2017-03-21 17:17:40]

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

[commit-bot: I haz the power, 2017-03-21 17:18:41]

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-03-21 19:41:12]

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

[commit-bot: I haz the power, 2017-03-21 19:41:13]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[sadrul, 2017-03-22 04:46:48]

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

[commit-bot: I haz the power, 2017-03-22 04:47:36]

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

[sadrul, 2017-03-22 04:47:49]

Description was changed from

==========
gpu: Replace GpuMsg_CollectGraphicsInfo with mojom API.

This introduces mojom.GpuService.RequestCompleteGpuInfo() API to replace
the GpuMsg_CollectGraphicsInfo chrome ipc message. This makes a subtle
change in how the response is handled: the response in the browser used
to be handled in the UI thread, but with this change, the response is
handled in the IO thread. However, the callback for the response notifies
the GpuDataManagerImpl instance, which can be accessed from both the IO
and UI threads. So this change should not affect the actual behaviour.

BUG=643746
==========

to

==========
gpu: Replace GpuMsg_CollectGraphicsInfo with mojom API.

This introduces mojom.GpuService.RequestCompleteGpuInfo() API to replace
the GpuMsg_CollectGraphicsInfo chrome ipc message.

BUG=643746
==========

[commit-bot: I haz the power, 2017-03-22 06:28:22]

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

[commit-bot: I haz the power, 2017-03-22 06:28:23]

Dry run: Try jobs failed on following builders:
  ios-simulator-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-xco...)

[sadrul, 2017-03-22 11:53:48]

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

[commit-bot: I haz the power, 2017-03-22 11:54:06]

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-03-22 13:40:23]

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

[commit-bot: I haz the power, 2017-03-22 13:40:24]

Dry run: This issue passed the CQ dry run.

[sadrul, 2017-03-22 15:28:02]

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

[commit-bot: I haz the power, 2017-03-22 15:28:18]

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

[sadrul, 2017-03-22 16:21:43]

The CQ bit was unchecked by sadrul@chromium.org

[sadrul, 2017-03-22 17:37:08]

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

[commit-bot: I haz the power, 2017-03-22 17:37:39]

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-03-22 18:49:39]

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

[commit-bot: I haz the power, 2017-03-22 18:49:40]

Dry run: Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[sadrul, 2017-03-23 00:49:40]

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

[commit-bot: I haz the power, 2017-03-23 00:50:16]

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

[sadrul, 2017-03-23 01:06:40]

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

[commit-bot: I haz the power, 2017-03-23 01:07:21]

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

[sadrul, 2017-03-23 01:51:00]

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

[commit-bot: I haz the power, 2017-03-23 01:51:15]

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-03-23 02:08:24]

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

[commit-bot: I haz the power, 2017-03-23 02:08:25]

Dry run: Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[sadrul, 2017-03-23 18:01:13]

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

[commit-bot: I haz the power, 2017-03-23 18:02:56]

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-03-23 18:12:45]

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

[commit-bot: I haz the power, 2017-03-23 18:12:46]

Dry run: Try jobs failed on following builders:
  cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...)

[sadrul, 2017-03-23 19:46:08]

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

[commit-bot: I haz the power, 2017-03-23 19:46:52]

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

[sadrul, 2017-03-23 19:47:54]

In case you are wondering what happened to this CL: it's causing some
somewhat-flaky test failures (telemetry_unittests) on windows trybots. I am
actively investigating (but not having a lot of luck with) the failures.

[commit-bot: I haz the power, 2017-03-23 20:06:25]

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

[commit-bot: I haz the power, 2017-03-23 20:06:26]

Dry run: Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[sadrul, 2017-03-23 21:41:38]

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

[commit-bot: I haz the power, 2017-03-23 21:42:23]

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-03-24 00:03:25]

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

[commit-bot: I haz the power, 2017-03-24 00:03:26]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[sadrul, 2017-03-24 01:30:59]

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

[commit-bot: I haz the power, 2017-03-24 01:31:28]

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-03-24 01:54:04]

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

[commit-bot: I haz the power, 2017-03-24 01:54:05]

Dry run: Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[sadrul, 2017-03-24 02:27:00]

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

[commit-bot: I haz the power, 2017-03-24 02:27:30]

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

[sadrul, 2017-03-24 02:51:02]

The CQ bit was unchecked by sadrul@chromium.org

[sadrul, 2017-03-24 03:18:01]

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

[commit-bot: I haz the power, 2017-03-24 03:18:31]

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-03-24 03:48:53]

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

[commit-bot: I haz the power, 2017-03-24 03:48:54]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[sadrul, 2017-03-24 04:06:12]

Patchset #21 (id:390001) has been deleted

[sadrul, 2017-03-24 04:13:24]

The flakiness seems to have gone away ... I will put it in the CQ and keep an
eye on the subsequent CQ runs if/when this lands.

[sadrul, 2017-03-24 04:15:01]

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

[commit-bot: I haz the power, 2017-03-24 04:15:15]

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

[sadrul, 2017-03-24 04:54:44]

The CQ bit was unchecked by sadrul@chromium.org

[sadrul, 2017-03-24 15:51:31]

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

[commit-bot: I haz the power, 2017-03-24 15:52:22]

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-03-24 16:50:58]

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

[commit-bot: I haz the power, 2017-03-24 16:50:59]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[sadrul, 2017-03-24 17:30:31]

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

[commit-bot: I haz the power, 2017-03-24 17:31:07]

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-03-24 18:25:06]

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

[commit-bot: I haz the power, 2017-03-24 18:25:07]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[sadrul, 2017-03-25 00:26:34]

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

[commit-bot: I haz the power, 2017-03-25 00:26:58]

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-03-25 01:22:10]

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

[commit-bot: I haz the power, 2017-03-25 01:22:11]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[sadrul, 2017-03-25 02:44:45]

The CQ bit was checked by sadrul@chromium.org

[sadrul, 2017-03-25 02:44:46]

The patchset sent to the CQ was uploaded after l-g-t-m from tsepez@chromium.org,
piman@chromium.org
Link to the patchset: https://codereview.chromium.org/2753293003/#ps460001
(title: "tot merge")

[commit-bot: I haz the power, 2017-03-25 02:45:02]

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-03-25 02:51:34]

CQ is committing da patch.

Bot data: {"patchset_id": 460001, "attempt_start_ts": 1490409885886020,
"parent_rev": "e04370309e452bfdbad223228b908c7e31f2809c", "commit_rev":
"9e029acf8a371e301aefcb51b4863137adccde68"}

[commit-bot: I haz the power, 2017-03-25 02:52:46]

Description was changed from

==========
gpu: Replace GpuMsg_CollectGraphicsInfo with mojom API.

This introduces mojom.GpuService.RequestCompleteGpuInfo() API to replace
the GpuMsg_CollectGraphicsInfo chrome ipc message.

BUG=643746
==========

to

==========
gpu: Replace GpuMsg_CollectGraphicsInfo with mojom API.

This introduces mojom.GpuService.RequestCompleteGpuInfo() API to replace
the GpuMsg_CollectGraphicsInfo chrome ipc message.

BUG=643746

Review-Url: https://codereview.chromium.org/2753293003
Cr-Commit-Position: refs/heads/master@{#459632}
Committed:
https://chromium.googlesource.com/chromium/src/+/9e029acf8a371e301aefcb51b486...
==========

[commit-bot: I haz the power, 2017-03-25 02:52:48]

Committed patchset #24 (id:460001) as
https://chromium.googlesource.com/chromium/src/+/9e029acf8a371e301aefcb51b486...