Add ability to query and allocate zero copy buffers.

Add ability to query and allocate zero copy buffers.

BUG=

Committed: https://crrev.com/7b84691293a8aa7fe298a8c7be53af4af1444e79
Cr-Commit-Position: refs/heads/master@{#303470}

[alexst (slow to review), 2014-11-07 15:45:52]

Patchset #1 (id:1) has been deleted

[alexst (slow to review), 2014-11-07 15:47:05]

alexst@chromium.org changed reviewers:
+ spang@chromium.org

[alexst (slow to review), 2014-11-07 15:47:44]

Adding ability to allocate zero copy via ozone in anticipation of the new world
of better memory usage.

[spang, 2014-11-07 17:42:06]

https://codereview.chromium.org/706273002/diff/20001/ui/ozone/public/surface_...
File ui/ozone/public/surface_factory_ozone.h (right):

https://codereview.chromium.org/706273002/diff/20001/ui/ozone/public/surface_...
ui/ozone/public/surface_factory_ozone.h:72: MAP,
do we ever want both (MAP | SCANOUT)?

[alexst (slow to review), 2014-11-07 17:44:50]

On 2014/11/07 17:42:06, spang wrote:
>
https://codereview.chromium.org/706273002/diff/20001/ui/ozone/public/surface_...
> File ui/ozone/public/surface_factory_ozone.h (right):
> 
>
https://codereview.chromium.org/706273002/diff/20001/ui/ozone/public/surface_...
> ui/ozone/public/surface_factory_ozone.h:72: MAP,
> do we ever want both (MAP | SCANOUT)?

Nothing else in the system understands this yet, but the answer is potentially.
In that case we can just add MAP_SCANOUT as another enum

[spang, 2014-11-07 17:48:02]

lgtm

[alexst (slow to review), 2014-11-10 13:27:44]

The CQ bit was checked by alexst@chromium.org

[commit-bot: I haz the power, 2014-11-10 13:28:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/706273002/20001

[commit-bot: I haz the power, 2014-11-10 13:31:37]

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

[commit-bot: I haz the power, 2014-11-10 13:31:38]

Try jobs failed on following builders:
  linux_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu/builds/...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/79464)
  android_aosp on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_aosp/bu...)
  linux_chromium_asan_rel on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  win8_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_rel...)
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[alexst (slow to review), 2014-11-10 15:06:21]

The CQ bit was checked by alexst@chromium.org

[commit-bot: I haz the power, 2014-11-10 15:07:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/706273002/40001

[commit-bot: I haz the power, 2014-11-10 15:52:14]

Committed patchset #2 (id:40001)

[commit-bot: I haz the power, 2014-11-10 15:53:37]

Patchset 2 (id:??) landed as
https://crrev.com/7b84691293a8aa7fe298a8c7be53af4af1444e79
Cr-Commit-Position: refs/heads/master@{#303470}