diff options
| author | boliu@chromium.org <boliu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-13 04:00:49 +0000 |
|---|---|---|
| committer | boliu@chromium.org <boliu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-13 04:00:49 +0000 |
| commit | 40245ccfa40e45cd002830cc9170fdd0b8578d00 (patch) | |
| tree | fb593832c869799b0ce4249441067cda3326463a /gpu/command_buffer/service/gles2_cmd_decoder_unittest_2.cc | |
| parent | 7300a267b737821996da4efd4b89ac216308c59e (diff) | |
| download | chromium_src-40245ccfa40e45cd002830cc9170fdd0b8578d00.zip chromium_src-40245ccfa40e45cd002830cc9170fdd0b8578d00.tar.gz chromium_src-40245ccfa40e45cd002830cc9170fdd0b8578d00.tar.bz2 | |
[Android] Add workaround to unbind gpu memory buffer only on NVIDIA
For gralloc backed gpu memory buffer on Android, it is undefined whether
locking for read/write while the buffer is bound to a texture is
allowed.
On nvidia devices (eg 2012 nexus 7), lock without unbind will lead to
deadlocks in the driver (crbug.com/264096).
However on other nexus gpu vendors (img, arm, qualcomm), unbind is very
expensive since it flushes the gpu pipeline. And vendors have advised
that lock while bound is allowed and is the right solution to this
slowness, as long as the texture is eventually recycled or deleted.
Add a workaround for nvidia to only unbind in GLImage::DidUseTexImage.
BUG=
Review URL: https://codereview.chromium.org/66033009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@234740 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'gpu/command_buffer/service/gles2_cmd_decoder_unittest_2.cc')
0 files changed, 0 insertions, 0 deletions