New issue
Advanced search Search tips

Issue 864914 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 3
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug

Blocking:
issue 820047



Sign in to add a comment

[ozone/wayland] enable native memory buffers with Wayland backend.

Project Member Reported by msi...@igalia.com, Jul 18

Issue description

Blocking: 820047
Status: Assigned (was: Available)
Cc: je_julie.kim@chromium.org
Summary: [ozone/wayland] enable software rasterization with Wayland backend. (was: enable software rasterization with Wayland backend.)
Summary: [ozone/wayland] enable native memory buffers with Wayland backend. (was: [ozone/wayland] enable software rasterization with Wayland backend.)
Project Member

Comment 5 by bugdroid1@chromium.org, Oct 23

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/80659f167bd7f06ffc093fdfd7da9f279211ab50

commit 80659f167bd7f06ffc093fdfd7da9f279211ab50
Author: Maksim Sisov <msisov@igalia.com>
Date: Tue Oct 23 16:54:28 2018

[ozone/wayland] Start using announced formats from ::Modifers call.

The zwp_linux_dmabuf interface says that both "modifier" and "format"
event calls announce supported fourcc formats. Thus, start using
both of them to store supported formats.

It's said that the "format" event call is going to be deprecated,
but "modifier" only works when zwp_linux_dmabuf version 3 is
supported by the compositor. As long as there are still systems with
zwp_linux_dmabuf version 1, use both "format" and "modifier"
event calls.

Also, increase supported zwp_linux_dmabuf version in
WaylandConnection.

Change-Id: Idad0c309e48370e831316f6e2353bc5cd1fd5c01
Bug:  864914 
Reviewed-on: https://chromium-review.googlesource.com/c/1296533
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#601988}
[modify] https://crrev.com/80659f167bd7f06ffc093fdfd7da9f279211ab50/ui/ozone/platform/wayland/wayland_buffer_manager.cc
[modify] https://crrev.com/80659f167bd7f06ffc093fdfd7da9f279211ab50/ui/ozone/platform/wayland/wayland_buffer_manager.h
[modify] https://crrev.com/80659f167bd7f06ffc093fdfd7da9f279211ab50/ui/ozone/platform/wayland/wayland_connection.cc

Project Member

Comment 6 by bugdroid1@chromium.org, Oct 23

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/97b0a4e0d017ca07ec3e2cbb35a63860c29bdcdf

commit 97b0a4e0d017ca07ec3e2cbb35a63860c29bdcdf
Author: Michael Spang <spang@chromium.org>
Date: Tue Oct 23 19:23:40 2018

Whitelist dmabuf sync ioctl on all linux platforms

This ioctl is used to synchronize zero copy GPU uploads. Non-Chrome OS
builds are starting to be able to use this capability (wayland on linux
desktop, non-CrOS DRM platform builds) so whitelist it more broadly.

Bug:  898234 ,  864914 
Test: chrome --enable-zero-copy --enable-native-gpu-memory-buffers
  on http://media.24ways.org/2009/15/space.html w/ fps counter

Change-Id: I449d5deddd48abff65a7f7add9c3b990f8d208e3
Reviewed-on: https://chromium-review.googlesource.com/c/1297085
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602049}
[modify] https://crrev.com/97b0a4e0d017ca07ec3e2cbb35a63860c29bdcdf/services/service_manager/sandbox/linux/bpf_renderer_policy_linux.cc

Project Member

Comment 7 by bugdroid1@chromium.org, Oct 28

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0057ae52fe0eb275454286d4ed8cce49f3304ccc

commit 0057ae52fe0eb275454286d4ed8cce49f3304ccc
Author: Maksim Sisov <msisov@igalia.com>
Date: Sun Oct 28 17:13:20 2018

[ozone/wayland] Enable native gpu memory buffers support

This patch enables native gpu memory buffers support by fixing compile
time assumptions in client_native_pixmap_factory_dmabuf.cc.

Now, the supports_import_from_dmabuf_ field is added to the
client_native_pixmap_factory_dmabuf.h class, and it is used to identify
whether *cpu_read_write buffer usages can be supported.

Bug:  864914 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: Ifd7d3c6d3906990a79521867ee4e6a826ce4c618
Reviewed-on: https://chromium-review.googlesource.com/c/1238154
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Reviewed-by: Michael Spang <spang@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/heads/master@{#603384}
[modify] https://crrev.com/0057ae52fe0eb275454286d4ed8cce49f3304ccc/ui/gfx/linux/client_native_pixmap_factory_dmabuf.cc
[modify] https://crrev.com/0057ae52fe0eb275454286d4ed8cce49f3304ccc/ui/gfx/linux/client_native_pixmap_factory_dmabuf.h
[modify] https://crrev.com/0057ae52fe0eb275454286d4ed8cce49f3304ccc/ui/ozone/platform/wayland/client_native_pixmap_factory_wayland.cc
[modify] https://crrev.com/0057ae52fe0eb275454286d4ed8cce49f3304ccc/ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc
[modify] https://crrev.com/0057ae52fe0eb275454286d4ed8cce49f3304ccc/ui/ozone/platform/wayland/wayland_buffer_manager.cc

Status: Fixed (was: Assigned)

Sign in to add a comment