content: Use mus client-lib's gpu-service from renderers.

content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

Notable changes.
. Introduce content::GpuClient in content-browser as the implementation
  of the mojom::Gpu interface. The GpuClient currently implements the
  interface with the existing code. In future CLs, this will be updated
  to look more like ui::ws::GpuClient.
. RenderProcessHostImpl creates and owns the GpuClient for each renderer
  process. The GpuClient lives and operates on the IO thread.
. ui::Gpu is created and owned by the RenderThreadImpl (as it is right
  now in --mash mode).
. ui::Gpu is updated to work with a service_manager::InterfaceProvider
  (which is available in a regular chrome) if a Connector is unavailable.

BUG=643746
Committed: https://crrev.com/53546591865acbacdc0a3e229933f591b3f08f2d
Cr-Commit-Position: refs/heads/master@{#439282}

[sadrul, 2016-11-18 19:39:29]

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

[commit-bot: I haz the power, 2016-11-18 19:40:32]

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-11-18 19:50:10]

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

[commit-bot: I haz the power, 2016-11-18 19:50:11]

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, 2016-11-18 20:52:00]

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

[commit-bot: I haz the power, 2016-11-18 20:52:43]

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

[sadrul, 2016-11-18 21:01:14]

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

[commit-bot: I haz the power, 2016-11-18 21:02:33]

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-11-18 21:29:04]

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

[commit-bot: I haz the power, 2016-11-18 21:29:04]

Dry run: Try jobs failed on following builders:
  android_compile_dbg on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...)

[sadrul, 2016-11-19 03:06:21]

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

[commit-bot: I haz the power, 2016-11-19 03:06: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-11-19 04:07:10]

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

[commit-bot: I haz the power, 2016-11-19 04:07:10]

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, 2016-11-19 05:38:56]

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

[commit-bot: I haz the power, 2016-11-19 05:39: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, 2016-11-19 05:45:57]

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

[commit-bot: I haz the power, 2016-11-19 05:45:58]

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

[sadrul, 2016-11-19 06:12:17]

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

[commit-bot: I haz the power, 2016-11-19 06:12:24]

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

[sadrul, 2016-11-19 07:01:06]

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

[commit-bot: I haz the power, 2016-11-19 07:01: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, 2016-11-19 07:22:56]

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

[commit-bot: I haz the power, 2016-11-19 07:22:57]

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, 2016-11-20 02:52:19]

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

[commit-bot: I haz the power, 2016-11-20 02:52:32]

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-11-20 03:21:49]

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

[commit-bot: I haz the power, 2016-11-20 03:21:50]

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, 2016-11-30 05:45:06]

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

[commit-bot: I haz the power, 2016-11-30 05:45: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, 2016-11-30 06:28:28]

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

[commit-bot: I haz the power, 2016-11-30 06:28:29]

Dry run: Try jobs failed on following builders:
  android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...)

[sadrul, 2016-11-30 18:00:28]

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

[commit-bot: I haz the power, 2016-11-30 18:01: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, 2016-11-30 18:04:39]

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

[commit-bot: I haz the power, 2016-11-30 18:04:40]

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, 2016-11-30 18:57:36]

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

[commit-bot: I haz the power, 2016-11-30 18:58:33]

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-11-30 19:34:31]

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

[commit-bot: I haz the power, 2016-11-30 19:34:32]

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, 2016-11-30 20:09:41]

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

[commit-bot: I haz the power, 2016-11-30 20:10:10]

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-11-30 20:50:02]

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

[commit-bot: I haz the power, 2016-11-30 20:50:03]

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

[sadrul, 2016-12-01 00:52:43]

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

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

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-12-01 01:33:06]

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

[commit-bot: I haz the power, 2016-12-01 01:33:07]

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, 2016-12-01 02:23:09]

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

[commit-bot: I haz the power, 2016-12-01 02:23:34]

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

[sadrul, 2016-12-01 02:53:26]

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

[commit-bot: I haz the power, 2016-12-01 02:53:42]

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-12-01 03:09:41]

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

[commit-bot: I haz the power, 2016-12-01 03:09:42]

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, 2016-12-01 03:13:46]

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

[commit-bot: I haz the power, 2016-12-01 03:14: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, 2016-12-01 04:10:30]

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

[commit-bot: I haz the power, 2016-12-01 04:10:31]

Dry run: Try jobs failed on following builders:
  android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...)

[sadrul, 2016-12-07 17:15:20]

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

[commit-bot: I haz the power, 2016-12-07 17:15: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, 2016-12-07 17:57:03]

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

[commit-bot: I haz the power, 2016-12-07 17:57:04]

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, 2016-12-09 02:18:04]

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

[commit-bot: I haz the power, 2016-12-09 02:19:03]

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-12-09 02:34:30]

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

[commit-bot: I haz the power, 2016-12-09 02:34:31]

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

[sadrul, 2016-12-09 16:24:45]

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

[commit-bot: I haz the power, 2016-12-09 16:24:57]

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-12-09 16:41:22]

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

[commit-bot: I haz the power, 2016-12-09 16:41:23]

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, 2016-12-09 17:42:02]

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

[commit-bot: I haz the power, 2016-12-09 17:42:27]

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-12-09 18:09:29]

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

[commit-bot: I haz the power, 2016-12-09 18:09:30]

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, 2016-12-09 20:55:58]

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

[commit-bot: I haz the power, 2016-12-09 20:57:08]

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

[sadrul, 2016-12-09 21:07:50]

Description was changed from

==========
content: Use mus client-lib's gpu-service from renderers.

...

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

to

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

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

[sadrul, 2016-12-09 21:17:02]

Description was changed from

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

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

to

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

Notable changes.
. Introduce content::GpuClient in content-browser as the implementation
  of the mojom::Gpu interface.
. RenderProcessHostImpl creates and owns the GpuClient for each renderer
  process. The GpuClient lives and operates on the IO thread.
. ui::Gpu is created and owned by the RenderThreadImpl (as it is right
  now in --mash mode).
. ui::Gpu is updated to work with a service_manager::InterfaceProvider
  (which is available in a regular chrome) if a Connector is unavailable.

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

[sadrul, 2016-12-09 21:20:35]

Description was changed from

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

Notable changes.
. Introduce content::GpuClient in content-browser as the implementation
  of the mojom::Gpu interface.
. RenderProcessHostImpl creates and owns the GpuClient for each renderer
  process. The GpuClient lives and operates on the IO thread.
. ui::Gpu is created and owned by the RenderThreadImpl (as it is right
  now in --mash mode).
. ui::Gpu is updated to work with a service_manager::InterfaceProvider
  (which is available in a regular chrome) if a Connector is unavailable.

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

to

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

Notable changes.
. Introduce content::GpuClient in content-browser as the implementation
  of the mojom::Gpu interface. The GpuClient currently implements the
  interface with the existing code. In future CLs, this will be updated
  to look more like ui::ws::GpuClient.
. RenderProcessHostImpl creates and owns the GpuClient for each renderer
  process. The GpuClient lives and operates on the IO thread.
. ui::Gpu is created and owned by the RenderThreadImpl (as it is right
  now in --mash mode).
. ui::Gpu is updated to work with a service_manager::InterfaceProvider
  (which is available in a regular chrome) if a Connector is unavailable.

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

[sadrul, 2016-12-09 21:25:53]

sadrul@chromium.org changed reviewers:
+ ben@chromium.org, jam@chromium.org, reveman@chromium.org

[sadrul, 2016-12-09 21:25:55]

Hello!

reveman@ Would you mind reviewing this since this affects how GPU memory buffers
are allocated in the renderer? Thanks!

ben@ for content/browser/

jam@ for content/child and content/renderer

Please feel free to send to additional/different owners as you see fit. Thank
you!

/cc a few folks FYI.

[commit-bot: I haz the power, 2016-12-09 22:03:39]

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

[commit-bot: I haz the power, 2016-12-09 22:03:40]

Dry run: Try jobs failed on following builders:
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[jam, 2016-12-10 00:05:52]

lgtm

[sadrul, 2016-12-12 19:29:04]

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

[sadrul, 2016-12-12 19:29:05]

+tsepez@ for content/common and the manifest file in content/public/app/mojo

+jbauman@ is a gpu owner

[Tom Sepez, 2016-12-12 19:42:41]

lgtm

[reveman, 2016-12-12 21:59:23]

reveman@chromium.org changed reviewers:
+ hshi@chromium.org

[reveman, 2016-12-12 21:59:24]

lgtm % hshi's review who recently fixed some gpu process startup race conditions
on cros that we need to make sure are still handled correctly

[sadrul, 2016-12-12 23:26:32]

On 2016/12/12 21:59:24, reveman wrote:
> lgtm % hshi's review who recently fixed some gpu process startup race
conditions
> on cros that we need to make sure are still handled correctly

Thanks! Note that this makes the change in the renderer process, and leaves the
chrome-gpu process as it is, i.e. any fixes that went in for the chrome-gpu (or
chrome-browser) process will still be active for this. (is there a [relatively]
easy way to test/verify?)

[jbauman, 2016-12-13 03:28:04]

lgtm

[reveman, 2016-12-13 15:02:45]

On 2016/12/12 at 23:26:32, sadrul wrote:
> On 2016/12/12 21:59:24, reveman wrote:
> > lgtm % hshi's review who recently fixed some gpu process startup race
conditions
> > on cros that we need to make sure are still handled correctly
> 
> Thanks! Note that this makes the change in the renderer process, and leaves
the chrome-gpu process as it is, i.e. any fixes that went in for the chrome-gpu
(or chrome-browser) process will still be active for this. (is there a
[relatively] easy way to test/verify?)

You probably have to instrument the code to test this in a reliable way. Try
changing
https://cs.chromium.org/chromium/src/cc/raster/staging_buffer_pool.cc?l=35 to
0ms so buffers are not reused and then run some raster heave page like
https://cs.chromium.org/chromium/src/tools/perf/page_sets/tough_texture_uploa...
and randomly kill the gpu process.

Also, native GMBs have been disabled temporarily so you'll need to pass
--enable-native-gpu-memory-buffers to chrome on a intel chromebook for native
GMB code to be exercised for tiles.

[sadrul, 2016-12-16 06:35:34]

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

[commit-bot: I haz the power, 2016-12-16 06:35:50]

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

[sadrul, 2016-12-16 07:07:29]

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

[commit-bot: I haz the power, 2016-12-16 07:07: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, 2016-12-16 08:20:45]

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

[commit-bot: I haz the power, 2016-12-16 08:20:46]

Dry run: Try jobs failed on following builders:
  android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...)

[sadrul, 2016-12-16 19:27:18]

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

[commit-bot: I haz the power, 2016-12-16 19:28:20]

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-12-16 22:33:56]

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

[commit-bot: I haz the power, 2016-12-16 22:33:58]

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

[sadrul, 2016-12-17 00:36:24]

The CQ bit was checked by sadrul@chromium.org

[sadrul, 2016-12-17 00:36:24]

The patchset sent to the CQ was uploaded after l-g-t-m from
reveman@chromium.org, jam@chromium.org, jbauman@chromium.org,
tsepez@chromium.org
Link to the patchset: https://codereview.chromium.org/2514923002/#ps480001
(title: ".")

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

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-12-17 01:44:26]

CQ is committing da patch.

Bot data: {"patchset_id": 480001, "attempt_start_ts": 1481934984146960,
"parent_rev": "ccfce6158be289147844f8a946748155717b4bc3", "commit_rev":
"16e3b2262e150c1d9b4bac534ad1cf9ec8396d4b"}

[commit-bot: I haz the power, 2016-12-17 01:44:58]

Description was changed from

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

Notable changes.
. Introduce content::GpuClient in content-browser as the implementation
  of the mojom::Gpu interface. The GpuClient currently implements the
  interface with the existing code. In future CLs, this will be updated
  to look more like ui::ws::GpuClient.
. RenderProcessHostImpl creates and owns the GpuClient for each renderer
  process. The GpuClient lives and operates on the IO thread.
. ui::Gpu is created and owned by the RenderThreadImpl (as it is right
  now in --mash mode).
. ui::Gpu is updated to work with a service_manager::InterfaceProvider
  (which is available in a regular chrome) if a Connector is unavailable.

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

to

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

Notable changes.
. Introduce content::GpuClient in content-browser as the implementation
  of the mojom::Gpu interface. The GpuClient currently implements the
  interface with the existing code. In future CLs, this will be updated
  to look more like ui::ws::GpuClient.
. RenderProcessHostImpl creates and owns the GpuClient for each renderer
  process. The GpuClient lives and operates on the IO thread.
. ui::Gpu is created and owned by the RenderThreadImpl (as it is right
  now in --mash mode).
. ui::Gpu is updated to work with a service_manager::InterfaceProvider
  (which is available in a regular chrome) if a Connector is unavailable.

BUG=643746

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

[commit-bot: I haz the power, 2016-12-17 01:45:02]

Committed patchset #25 (id:480001)

[commit-bot: I haz the power, 2016-12-17 01:48:24]

Description was changed from

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

Notable changes.
. Introduce content::GpuClient in content-browser as the implementation
  of the mojom::Gpu interface. The GpuClient currently implements the
  interface with the existing code. In future CLs, this will be updated
  to look more like ui::ws::GpuClient.
. RenderProcessHostImpl creates and owns the GpuClient for each renderer
  process. The GpuClient lives and operates on the IO thread.
. ui::Gpu is created and owned by the RenderThreadImpl (as it is right
  now in --mash mode).
. ui::Gpu is updated to work with a service_manager::InterfaceProvider
  (which is available in a regular chrome) if a Connector is unavailable.

BUG=643746

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

to

==========
content: Use mus client-lib's gpu-service from renderers.

Switch over to using the gpu service from renderer processes on all
platforms. The service is used to create the gpu-channel, and allocate
gpu memory buffers.

Notable changes.
. Introduce content::GpuClient in content-browser as the implementation
  of the mojom::Gpu interface. The GpuClient currently implements the
  interface with the existing code. In future CLs, this will be updated
  to look more like ui::ws::GpuClient.
. RenderProcessHostImpl creates and owns the GpuClient for each renderer
  process. The GpuClient lives and operates on the IO thread.
. ui::Gpu is created and owned by the RenderThreadImpl (as it is right
  now in --mash mode).
. ui::Gpu is updated to work with a service_manager::InterfaceProvider
  (which is available in a regular chrome) if a Connector is unavailable.

BUG=643746

Committed: https://crrev.com/53546591865acbacdc0a3e229933f591b3f08f2d
Cr-Commit-Position: refs/heads/master@{#439282}
==========

[commit-bot: I haz the power, 2016-12-17 01:48:26]

Patchset 25 (id:??) landed as
https://crrev.com/53546591865acbacdc0a3e229933f591b3f08f2d
Cr-Commit-Position: refs/heads/master@{#439282}