Propagate kForceGpuMemAvailableMb flag to the renderer.

Propagate kForceGpuMemAvailableMb flag to the renderer.

This flag is used in the renderer to override the memory limit for
tiles. The code to actually override the memory is already there, but
the flag isn't currently being propagated to the renderer. This patch
fixes this.

R=enne@chromium.org

Review-Url: https://codereview.chromium.org/2616773002
Cr-Commit-Position: refs/heads/master@{#443033}
Committed: https://chromium.googlesource.com/chromium/src/+/dd0efaefeb00163421f31ed74880d0d9a5c5b241

[vmpstr, 2017-01-05 00:20:32]

vmpstr@chromium.org changed reviewers:
+ achuith@chromium.org, ccameron@chromium.org

[vmpstr, 2017-01-05 00:20:32]

Please take a look.

[ccameron, 2017-01-05 00:42:30]

lgtm

[enne (OOO), 2017-01-05 01:16:45]

lgtm

[vmpstr, 2017-01-05 18:58:03]

achuithb@ could you take a look at
chrome/browser/chromeos/login/chrome_restart_request.cc please?

[achuithb, 2017-01-10 14:54:04]

On 2017/01/05 18:58:03, vmpstr wrote:
> achuithb@ could you take a look at
> chrome/browser/chromeos/login/chrome_restart_request.cc please?

lgtm

[vmpstr, 2017-01-10 19:29:18]

The CQ bit was checked by vmpstr@chromium.org

[commit-bot: I haz the power, 2017-01-10 19:29:55]

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-10 19:45:06]

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

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

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_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[vmpstr, 2017-01-11 18:58:07]

The CQ bit was checked by vmpstr@chromium.org

[vmpstr, 2017-01-11 18:58:08]

The patchset sent to the CQ was uploaded after l-g-t-m from
achuith@chromium.org, enne@chromium.org, ccameron@chromium.org
Link to the patchset: https://codereview.chromium.org/2616773002/#ps20001
(title: "fix")

[commit-bot: I haz the power, 2017-01-11 18:58:36]

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-11 22:52:55]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1484161087607350,
"parent_rev": "ebb08805ae19aa64793d42f13eeb965363f5ab5c", "commit_rev":
"dd0efaefeb00163421f31ed74880d0d9a5c5b241"}

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

Description was changed from

==========
Propagate kForceGpuMemAvailableMb flag to the renderer.

This flag is used in the renderer to override the memory limit for
tiles. The code to actually override the memory is already there, but
the flag isn't currently being propagated to the renderer. This patch
fixes this.

R=enne@chromium.org
==========

to

==========
Propagate kForceGpuMemAvailableMb flag to the renderer.

This flag is used in the renderer to override the memory limit for
tiles. The code to actually override the memory is already there, but
the flag isn't currently being propagated to the renderer. This patch
fixes this.

R=enne@chromium.org

Review-Url: https://codereview.chromium.org/2616773002
Cr-Commit-Position: refs/heads/master@{#443033}
Committed:
https://chromium.googlesource.com/chromium/src/+/dd0efaefeb00163421f31ed74880...
==========

[commit-bot: I haz the power, 2017-01-11 22:53:26]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/dd0efaefeb00163421f31ed74880...