summaryrefslogtreecommitdiffstats
path: root/gpu
Commit message (Collapse)AuthorAgeFilesLines
* GPU Tracer no longer issue device traces when device category is off.dyen2015-04-113-31/+70
| | | | | | | | | R=vmiura@chromium.org BUG=None Review URL: https://codereview.chromium.org/1081483002 Cr-Commit-Position: refs/heads/master@{#324736}
* Add VDA supported profile to GPUInfohenryhsu2015-04-104-15/+48
| | | | | | | | | | | | | | | Different CrOS devices have different supported decode profiles. Add VDA supported profile to GPUInfo so this can be detected in runtime. This is also the preparation of removing --ignore-resolution-limits-for-accelerated-video-decode flag. BUG=350197 TEST=Play a video on Exynos and Intel CrOS devices and make sure Media.GpuVideoDecoderInitializeStatus is 0. Review URL: https://codereview.chromium.org/795633005 Cr-Commit-Position: refs/heads/master@{#324596}
* [Android] Move testing/android/ to testing/android/native_test/jbudorick2015-04-091-1/+1
| | | | | | | | | | | This will let us put android test code unrelated to native test APK wrapping elsewhere in testing/android/*. BUG= Review URL: https://codereview.chromium.org/1071573003 Cr-Commit-Position: refs/heads/master@{#324512}
* Make ui/gl depend on the necessary runtime targets on Windows.jam2015-04-091-8/+0
| | | | | | | | | Committed: https://crrev.com/f4a6e44ff20c29a6410a698a06a45dd11666ef53 Cr-Commit-Position: refs/heads/master@{#324320} Review URL: https://codereview.chromium.org/1070933002 Cr-Commit-Position: refs/heads/master@{#324445}
* Revert of Make ui/gl depend on the necessary runtime targets on Windows. ↵engedy2015-04-091-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (patchset #3 id:40001 of https://codereview.chromium.org/1070933002/) Reason for revert: This CL introduces a typo to the GN build file, so that Windows GN builds fail. It should be possible to reland after below line is changed from appending to assignment. ERROR at //ui/gl/BUILD.gn:203:5: Undefined variable for +=. data_deps += [ ^-------- I don't have something with this name in scope now. See: http://build.chromium.org/p/chromium.win/builders/Win8%20GN Original issue's description: > Make ui/gl depend on the necessary runtime targets on Windows. > > Committed: https://crrev.com/f4a6e44ff20c29a6410a698a06a45dd11666ef53 > Cr-Commit-Position: refs/heads/master@{#324320} TBR=brettw@chromium.org,scottmg@chromium.org,jam@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1071113002 Cr-Commit-Position: refs/heads/master@{#324404}
* Make ui/gl depend on the necessary runtime targets on Windows.jam2015-04-091-8/+0
| | | | | | Review URL: https://codereview.chromium.org/1070933002 Cr-Commit-Position: refs/heads/master@{#324320}
* gpu: Add UMA statistic for RG texture support.reveman2015-04-081-0/+1
| | | | | | | | BUG= Review URL: https://codereview.chromium.org/1068133002 Cr-Commit-Position: refs/heads/master@{#324310}
* Add R_8 GPU memory buffers format.dcastagna2015-04-087-4/+35
| | | | | | | | | | | | | | | | GpuMemoryBuffer::Format::R_8 should be used to represent textures with only one channel, the associated image should have GL_R8/GL_R8_EXT as internal format. With this CL the only implementation of GpuMemoryBuffer that supports R_8 is GLImageMemory, it expects a 4 bytes row alignment (4 is the default value for GL_PACK_ALIGNMENT). BUG= Review URL: https://codereview.chromium.org/1051503003 Cr-Commit-Position: refs/heads/master@{#324281}
* Add a "Max. MSAA samples" entry to chrome://gpu.senorblanco2015-04-084-0/+13
| | | | | | | | BUG=474727 Review URL: https://codereview.chromium.org/1063233002 Cr-Commit-Position: refs/heads/master@{#324236}
* We started redesigning GpuMemoryBuffer interface to handle multiple buffers [0].emircan2015-04-083-5/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | [0] https://codereview.chromium.org/1024113003/#ps200001 In this CL: - I added a new format gfx::GpuMemoryBuffer::YUV_420 - Implemented helper functions to use with it on GpuMemoryBufferImpl. - I added support in GpuMemoryBufferImplSharedMemory and GpuMemoryBufferFactorySharedMemory - I added { gfx::GpuMemoryBuffer::YUV_420, gfx::GpuMemoryBuffer::MAP } as a supported config for testing - I added support for multi plane in test implementations: test_gpu_memory_buffer_manager, gl_manager, gpu_memory_buffer_impl_unittest The future steps are: - Add a new GL_* internalformat corresponding to YUV_420 - Implement support for YUV_420 in GpuMemoryBufferFactoryOzoneNativeBuffer, GLImageLinuxDMABuffer and SurfaceFactoryOzone - Expose file descriptors for gfx::GpuMemoryBuffer::YUV_420 via Map() or GpuMemoryBufferHandle struct Check usage of gbm_bo_get_fd() at the lowest gbmbuffer level - Add support in GLImageSharedMemory and GLImageMemory through Bind functions - Look for possible use cases of multiple buffers on Android, Mac, and Win platforms BUG=439520 TEST=content_unittests --gtest_filter=GpuMemoryBufferImplTests.* content_unittests --gtest_filter=GpuMemoryBufferFactoryTest.* gl_tests --gtest_filter=GpuMemoryBufferTest* Review URL: https://codereview.chromium.org/1062853002 Cr-Commit-Position: refs/heads/master@{#324190}
* Disable framebuffer discarding on Mali-4xx and clean up.aelias2015-04-075-27/+23
| | | | | | | | | | | | | | | | | | | | | | It seems all of the known bugs with Mali-400 are related to framebuffer discarding. Blacklist framebuffer discarding universally on Mali-400 and reenable ganesh and canvas where it was still blacklisted on Mali-400. There was a preexisting workaround applied to all ARM < 4.4 which was originally written in the context of Mali-T604; this explains why the bugs only reproed on some Mali-400 devices. Add a new one for all 4xx. Also, a recently added Nexus 6 workaround did essentially the same thing, but at the level of making the discard do nothing instead of not advertising the extension. In OpenGL ES 3, this is a core method so failing to advertise won't be sufficient, so merge the two workarounds and remove the "_ext_" from the name. BUG=449488,451230 Review URL: https://codereview.chromium.org/1068573004 Cr-Commit-Position: refs/heads/master@{#324152}
* GPU workaround to simulate Out of Memory errors with large texturesbajones2015-04-072-0/+11
| | | | | | | | BUG=445542 Review URL: https://codereview.chromium.org/1050043003 Cr-Commit-Position: refs/heads/master@{#324150}
* Add reveman@ as owner of *gpu_memory_buffer* files.dcastagna2015-04-071-0/+4
| | | | | | | | BUG= Review URL: https://codereview.chromium.org/1067033002 Cr-Commit-Position: refs/heads/master@{#324125}
* Test gpu memory buffers drawing directly to the backbuffer.dcastagna2015-04-071-31/+65
| | | | | | | | | | | | | | | | To test the lifecycle of a memory buffer we used to use glCopyTextureCHROMIUM. This has some limitations due to the extension spec (i.e: limited subset of formats), and doesn't test the general lifecycle of the memory buffer. This patch changes GpuMemoryBufferTest.Lifecycle to test the lifecycle of the GpuMemoryBuffer writing directly to the backbuffer. BUG= Review URL: https://codereview.chromium.org/1066073002 Cr-Commit-Position: refs/heads/master@{#324123}
* Disable Occlusion Query on MediaTek MT8135mckev2015-04-071-1/+17
| | | | | | | | | | | | | | | | | Devices with some versions of the MediaTek MT8135 GPU driver do not return values when an occlusion query is performed, which causes a hard CHECK to get hit in GLES2Implementation::GetQueryObjectuivEXT. This adds an entry to the GPU bug list for this device (which identifies as PowerVR Rogue Han), preventing occlusion queries from being used on affected devices and driver versions. BUG=474413 TEST=OcclusionQuery.Occlusion Review URL: https://codereview.chromium.org/1064773002 Cr-Commit-Position: refs/heads/master@{#324072}
* gpu: More specific internalformat requirements for CreateImageCHROMIUM.reveman2015-04-074-40/+18
| | | | | | | | | | | | This reduces the complexity of the code needed to validate internalformat and makes it easier to add new formats. BUG=474280 TEST=gl_tests --gtest_filter=GpuMemoryBufferTests/GpuMemoryBufferTest.Lifecycle/* Review URL: https://codereview.chromium.org/1068663002 Cr-Commit-Position: refs/heads/master@{#324007}
* Work on Windows GN component build.brettw2015-04-067-35/+108
| | | | | | | | | | | | | This makes ppapi_shared link. This required many changes to gpu to match the structure of GYP in both component and non-component modes. BUG=470212 CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:android_chromium_gn_compile_dbg,android_chromium_gn_compile_rel;tryserver.chromium.win:win8_chromium_gn_rel,win8_chromium_gn_dbg;tryserver.chromium.mac:mac_chromium_gn_rel,mac_chromium_gn_dbg Reland of https://codereview.chromium.org/1053203003/ Review URL: https://codereview.chromium.org/1061953002 Cr-Commit-Position: refs/heads/master@{#323966}
* Test gfx::GpuMemoryBuffer::BGRA_8888 GpuMemoryBuffer lifecycle.dcastagna2015-04-061-19/+99
| | | | | | | | | | | | | | | The test fixture GpuMemoryBufferTest has been parametrized in terms of gfx::GpuMemoryBuffer::Format so that GpuMemoryBufferTest.Lifecycle can be run with different gfx::GpuMemoryBuffer::Format. gfx::GpuMemoryBuffer::BGRA_8888 has been added along with the already present RGBA_8888. BUG= Review URL: https://codereview.chromium.org/1055143003 Cr-Commit-Position: refs/heads/master@{#323948}
* Revert of Work on Windows GN component build. (patchset #8 id:140001 of ↵pkotwicz2015-04-067-108/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | https://codereview.chromium.org/1053203003/) Reason for revert: Reverting the CL because I think that it broke the GN compile on Linux - See http://build.chromium.org/p/chromium.linux/builders/Linux%20GN/builds/26255/steps/compile/logs/stdio Original issue's description: > Work on Windows GN component build. > > This makes ppapi_shared link. This required many changes to gpu to match the structure of GYP in both component and non-component modes. > > BUG=470212 > CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:android_chromium_gn_compile_dbg,android_chromium_gn_compile_rel;tryserver.chromium.win:win8_chromium_gn_rel,win8_chromium_gn_dbg;tryserver.chromium.mac:mac_chromium_gn_rel,mac_chromium_gn_dbg > > Committed: https://crrev.com/b3c7880dc9e66ff449b23e2273b4f20abecba442 > Cr-Commit-Position: refs/heads/master@{#323937} TBR=dpranke@chromium.org,brettw@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=470212 Review URL: https://codereview.chromium.org/1057993004 Cr-Commit-Position: refs/heads/master@{#323942}
* Work on Windows GN component build.brettw2015-04-067-35/+108
| | | | | | | | | | | This makes ppapi_shared link. This required many changes to gpu to match the structure of GYP in both component and non-component modes. BUG=470212 CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:android_chromium_gn_compile_dbg,android_chromium_gn_compile_rel;tryserver.chromium.win:win8_chromium_gn_rel,win8_chromium_gn_dbg;tryserver.chromium.mac:mac_chromium_gn_rel,mac_chromium_gn_dbg Review URL: https://codereview.chromium.org/1053203003 Cr-Commit-Position: refs/heads/master@{#323937}
* Fix a few lints found while working on crrev.com/1051503003.dcastagna2015-04-065-16/+15
| | | | | | | | | BUG= TBR=piman@chromium.org Review URL: https://codereview.chromium.org/1057183002 Cr-Commit-Position: refs/heads/master@{#323932}
* Revert of Use the desktop GL core profile on Linux when ES3 support is ↵marcheu2015-04-045-36/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | requested. (patchset #3 id:40001 of https://codereview.chromium.org/1052153002/) Reason for revert: This causes Chrome rendering to break on some Chrome OS devices, see crbug.com/473891 for details Original issue's description: > Use the desktop GL core profile on Linux when ES3 support is requested. > > Request an OpenGL 4.2 context (the minimum version Chromium's WebGL > 2.0 prototype currently requires) on Linux when > --enable-unsafe-es3-apis is specified on the command line. > > Clean up the shader translator's selection of the GLSL output format. > > BUG=471960 > > Committed: https://crrev.com/0b17446f9591af9377d18c9ccfe50471651d6bc7 > Cr-Commit-Position: refs/heads/master@{#323658} TBR=piman@chromium.org,kbr@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=471960 Review URL: https://codereview.chromium.org/1054883004 Cr-Commit-Position: refs/heads/master@{#323866}
* Make CreateAndConsumeTexture always associate client_id with a service_idbajones2015-04-042-0/+113
| | | | | | | | BUG=472465 Review URL: https://codereview.chromium.org/1058833004 Cr-Commit-Position: refs/heads/master@{#323856}
* Use the desktop GL core profile on Linux when ES3 support is requested.kbr2015-04-035-26/+36
| | | | | | | | | | | | | | Request an OpenGL 4.2 context (the minimum version Chromium's WebGL 2.0 prototype currently requires) on Linux when --enable-unsafe-es3-apis is specified on the command line. Clean up the shader translator's selection of the GLSL output format. BUG=471960 Review URL: https://codereview.chromium.org/1052153002 Cr-Commit-Position: refs/heads/master@{#323658}
* Enable multisampled_render_to_texture on Qualcomm GPUs.senorblanco2015-04-021-3/+2
| | | | | | | | | | Unlike ES3 MSAA, this extension seems to work. BUG=449116 Review URL: https://codereview.chromium.org/1053013002 Cr-Commit-Position: refs/heads/master@{#323561}
* Work on GN Windows component build.brettw2015-04-023-17/+4
| | | | | | | | | | | | | | | | The platform window target was set up to be a component but had no compilation units. This patch removes the defines from both builds. Removes the gpu_memory_buffer_manager target. This was causing problems and no equivalent exists in GYP. Does some cleanup of Windows ldflags BUG=470212 R=jam TBR=rockot@chromium.org (device/bluetooth) Review URL: https://codereview.chromium.org/1019803003 Cr-Commit-Position: refs/heads/master@{#323432}
* Break up disable_multisampling blacklist entry.senorblanco2015-04-024-13/+19
| | | | | | | | | | | | Split disable_multisampling blacklist entry into disable_chromium_framebuffer_multisample and disable_framebuffer_texture_multisample. BUG=449116 Review URL: https://codereview.chromium.org/1050613003 Cr-Commit-Position: refs/heads/master@{#323375}
* Use scoped_ptr<T[]> for memory allocated with operator new[].dcheng2015-04-011-1/+1
| | | | | | | | BUG=none Review URL: https://codereview.chromium.org/1056703002 Cr-Commit-Position: refs/heads/master@{#323362}
* Turn ThreadPriority enum into an enum class.gab2015-04-012-4/+4
| | | | | | | | | | | | | | | | | | Adding some type safety as it is often used in close proximity with OS-level raw integer priorities. Also fixing nomenclature to use CHROMIUM_STYLE_ENUM_NAMES rather than kGoogleStyleEnumNames: https://www.chromium.org/developers/coding-style#Naming And lastly, sorting the declaration order by importance. TBR=jam BUG=456903 Review URL: https://codereview.chromium.org/1051863003 Cr-Commit-Position: refs/heads/master@{#323359}
* Whitelist all Mali-400 for canvas/GPU raster except known bad models.aelias2015-04-011-0/+20
| | | | | | | | | | | | | | | | | | | Most Mali-400 we've tested seem to have reasonable quality drivers, but there are a few bad apples. The Galaxy S3 Mini (GT-I8190N) I can repro corruption locally on. Also (though I've failed to locally repro issues with the following): we had past reports of problems on Galaxy S3 (GT-I9300) and Galaxy Note 2 (SPH-L900), and also reports of non-GPU-raster corruption issues on Galaxy S5 Mini (SM-G800F). Let's try to ship a whitelist expansion excluding specifically those. It's likely I'll need to add some more long-tail devices to this list based on user bug reports. BUG=451230,468808 Review URL: https://codereview.chromium.org/1039303002 Cr-Commit-Position: refs/heads/master@{#323150}
* Added support for desktop OpenGL's Core Profile on Mac OS X.kbr2015-03-3117-146/+386
| | | | | | | | | | | | | | | | | | | | | | | | Joint work with ccameron@, thanks to whom for the ImageTransportSurface changes and some of the others. When --enable-unsafe-es3-apis is specified, use the core profile rather than the compatibility profile for all OpenGL contexts on Mac OS X. This CL adds the core profile as another known GLImplementation which behaves mostly like OpenGL ES, but partly like desktop GL, and has some differences compared to both. It is likely that Chrome will upgrade to the Core Profile on all platforms using desktop OpenGL, and that support for the compatibility profile will be dropped. Tested with both regular and WebGL content, with all combinations of --enable-unsafe-es3-apis and --disable-remote-core-animation. BUG=470396 Review URL: https://codereview.chromium.org/1038763004 Cr-Commit-Position: refs/heads/master@{#323091}
* Port gles2_conform_test_windowless action to GN build.tfarina2015-03-311-1/+104
| | | | | | | | | | | | | | | | | | | | | | It requires internal test files, hence it was not tested. Partially tested on Linux with the following command lines: $ gn gen out-gn --args='internal_gles2_conform_tests' Formatted with the following command line: $ gn format --in-place gpu/gles2_conform_support/BUILD.gn BUG=432959 TEST=see above R=dpranke@chromium.org,sievers@chromium.org CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:android_chromium_gn_compile_dbg,android_chromium_gn_compile_rel;tryserver.chromium.win:win8_chromium_gn_rel,win8_chromium_gn_dbg;tryserver.chromium.mac:mac_chromium_gn_rel,mac_chromium_gn_dbg Review URL: https://codereview.chromium.org/1033373002 Cr-Commit-Position: refs/heads/master@{#323082}
* Add a stub implementation of khronos_glcts_test to the GN build.dpranke2015-03-311-0/+23
| | | | | | | | | | | | | | The bulk of the test suite requires internal test files, and so we'll defer porting it to GN to a later date, but for now at least we'll have a skeleton to hang that work on. R=kbr@chromium.org BUG=471903, 461019 CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:android_chromium_gn_compile_dbg,android_chromium_gn_compile_rel;tryserver.chromium.win:win8_chromium_gn_rel,win8_chromium_gn_dbg;tryserver.chromium.mac:mac_chromium_gn_rel,mac_chromium_gn_dbg Review URL: https://codereview.chromium.org/1041363002 Cr-Commit-Position: refs/heads/master@{#322976}
* Port generate_gles2_conform_embedded_files action to GN build.tfarina2015-03-271-0/+15
| | | | | | | | | | | | | | | | It requires internal test files, hence it was not tested. Partially tested on Linux with the following command lines: $ gn gen out-gn --args='internal_gles2_conform_tests' BUG=432959 TEST=see above R=dpranke@chromium.org,sievers@chromium.org Review URL: https://codereview.chromium.org/1041883002 Cr-Commit-Position: refs/heads/master@{#322639}
* Revert of Remove Qualcomm MSAA from blacklist for versions >= Lollipop. ↵timvolodine2015-03-271-7/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (patchset #2 id:20001 of https://codereview.chromium.org/1034933002/) Reason for revert: speculative revert, this probably broke the instrumentation-hammerhead-clankium-lmp bot: https://uberchromegw.corp.google.com/i/clank/builders/instrumentation-hammerhead-clankium-lmp also see crbug.com/471200. Original issue's description: > Remove Qualcomm MSAA from blacklist for versions >= Lollipop. > > BUG=449116 > > Committed: https://crrev.com/1e8ac18cbd0e503335e5062a677609c38d75f1be > Cr-Commit-Position: refs/heads/master@{#322472} TBR=kbr@chromium.org,senorblanco@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=449116 Review URL: https://codereview.chromium.org/1037303002 Cr-Commit-Position: refs/heads/master@{#322585}
* gpu: Add gles2_conform_test target to GN build.tfarina2015-03-272-0/+13
| | | | | | | | | | | | | | | | | The internal stuff will come later. Tested on Linux with the following command lines: $ gn gen out-gn $ ninja -C out-gn gles2_conform_test BUG=432959 TEST=see above R=dpranke@chromium.org,sievers@chromium.org Review URL: https://codereview.chromium.org/1038243002 Cr-Commit-Position: refs/heads/master@{#322573}
* Remove the blacklist on newer Nvidia Linux driversdbdaniel422015-03-271-1/+5
| | | | | | | | | | | | | The initial reason for the blacklist was a bug that is now fixed. A workaround was first developed in Chromium and then later Nvidia actually fixed the root of the problem in their driver. This patch removes the blacklist for 331.38 and newer drivers. BUG=469979 Review URL: https://codereview.chromium.org/1032483002 Cr-Commit-Position: refs/heads/master@{#322527}
* We redesigned the GpuMemoryBuffer interface to handle multiple buffers. ↵emircan2015-03-272-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These changes started with the purpose of making use of new EGL_LINUX_DMA_BUF_EXT capabilities[0] and followed by an attempt to change the high level API [1]. [0] https://code.google.com/p/chromium/issues/detail?id=439520 [1] https://codereview.chromium.org/962723002/ The future steps are: - Add new GPUMemoryBuffer format gfx::GpuMemoryBuffer::YUV_420 StrideInBytes() should take index as input - Implement multi buffer support on GpuMemoryBufferFactoryOzoneNativeBuffer Change BufferToPixmapMap as std::map<std::pair<uint32_t, uint32_t>, ScopedVector<NativePixmap> > so that we can create multiple pixmaps(file descriptors) for single GpuMemoryBufferId - Add support for multiple pixmaps in GLImageLinuxDMABuffer - Implement support for GpuMemoryBufferImplSharedMemory Change GpuMemoryBufferHandle to contain std::vector<base::SharedMemoryHandle> - Add support for GLImageSharedMemory and GLImageMemory - Look for possible use cases of multiple buffers on Android, Mac, and Win platforms The new functions added are as below: class GFX_EXPORT GpuMemoryBuffer { // Maps each plane of the buffer into the client's address space so it can be // written to by the CPU. A pointer to plane K is stored at index K-1 of the // |data| array. This call may block, for instance if the GPU needs to finish // accessing the buffer or if CPU caches need to be synchronized. Returns // false on failure. virtual bool Map(void** data) = 0; // Fills the stride in bytes for the each plane of the buffer. The stride of // plane K is stored at index K-1 of the |stride| array. virtual void GetStride(uint32* stride) const = 0; }; The classes effected by this change is as below(except the test implementations). Currently none of them supports multiple buffers as the format doesn't exist. They are going to be implemented per platform in future CLs. +---------------+ |GpuMemoryBuffer| +------+--------+ | +--------+----------+ |GpuMemoryBufferImpl| ++----+-----+------++ | | | | | | | | +------------------------------++ | | +--+-------------------------+ |GpuMemoryBufferImplSharedMemory| | | |GpuMemoryBufferImplIOSurface| +-------------------------------+ | | +----------------------------+ | | +-----------------------------------++ +-+-------------------------------+ |GpuMemoryBufferImplOzoneNatiVeBuffer| |GpuMemoryBufferImplSurfaceTexture| +------------------------------------+ +---------------------------------+ |ui::GpuMemoryBufferFactory | |OzoneNatiVeBuffer | | INITALIZES | | ui::GLImageOzoneNatiVePixmapDmaBuf | | OR | | ui::GLImageOzoneNatiVePixmap | +------------------------------------+ BUG=439520 TEST= GpuMemoryBufferTest.* in gl_tests and GpuMemoryBufferImplTest.* in content_unittests. Review URL: https://codereview.chromium.org/1024113003 Cr-Commit-Position: refs/heads/master@{#322503}
* Only destroy GPUTracer if the pointer is not empty.dyen2015-03-261-2/+4
| | | | | | | | | R=vmiura@chromium.org BUG=471049, 467202 Review URL: https://codereview.chromium.org/1033093002 Cr-Commit-Position: refs/heads/master@{#322498}
* Remove Qualcomm MSAA from blacklist for versions >= Lollipop.senorblanco2015-03-261-2/+6
| | | | | | | | BUG=449116 Review URL: https://codereview.chromium.org/1034933002 Cr-Commit-Position: refs/heads/master@{#322472}
* gpu: Fix some jmadill's TODOs.tfarina2015-03-262-13/+8
| | | | | | | | | | BUG=None TEST=./build/gyp_chromium still works R=sievers@chromium.org Review URL: https://codereview.chromium.org/1038743003 Cr-Commit-Position: refs/heads/master@{#322445}
* Added FBO Invalidation workaround for Nexus 6.dyen2015-03-263-1/+19
| | | | | | | | | | | | | | | | | | We have run into a driver issue where after we invalidate a Frame Buffer Object it gets into a state where it will randomly drop draw calls and/or texture copies. I have added a workaround for this issue by skipping frame buffer invalidations on Adreno 420s. This is valid because invalidations set the frame buffer to be in an undefined state so skipping them is technically okay, however we may lose optimizations that could happen at the driver level for operations being performed on an undefined FBO. R=sievers@chromium.org, vmiura@chromium.org BUG=443060 Review URL: https://codereview.chromium.org/1034663003 Cr-Commit-Position: refs/heads/master@{#322403}
* Added Destroy() functions for GPUTimer and GPUTracer/GPUTrace.dyen2015-03-265-19/+68
| | | | | | | | | BUG=467202 TEST=Shut down during gpu.device trace has no warnings. Review URL: https://codereview.chromium.org/1018773002 Cr-Commit-Position: refs/heads/master@{#322304}
* Remove all usages of MojoGLES2GetGLES2Interface().alhaad2015-03-261-14/+6
| | | | | | | | | | | All html_viewer entry points now have Mojo C thunks. R=piman@chromium.org BUG=453591 Review URL: https://codereview.chromium.org/1035813002 Cr-Commit-Position: refs/heads/master@{#322275}
* Have compositor_model_bench target near its source files.tfarina2015-03-253-23/+29
| | | | | | | | | | | | | It is more traditional (and recommended) to have GN targets closer to the source files it builds. BUG=432959 TEST=gn gen out-gn && ninja -C out-gn compositor_model_bench R=sievers@chromium.org, dpranke@chromium.org Review URL: https://codereview.chromium.org/1032193002 Cr-Commit-Position: refs/heads/master@{#322226}
* Time of first use cost of upload.siva.gunturi2015-03-251-1/+6
| | | | | | | | | | | | This test is to check whether there is a time-of-first-use cost (e.g. driver doesn't upload to the texture until we draw with it). BUG= 423481 Review URL: https://codereview.chromium.org/1031463002 Cr-Commit-Position: refs/heads/master@{#322131}
* Add ANGLE perf tests targets.jmadill2015-03-242-0/+47
| | | | | | | | | | | | | This will enable building the ANGLE perf tests on Windows perf bot builders. BUG=angleproject:744 BUG=468852 R=sievers@chromium.org, thakis@chromium.org Review URL: https://codereview.chromium.org/1021763002 Cr-Commit-Position: refs/heads/master@{#322078}
* Remove |level| in copy(Sub)TextureCHROMIUM().dongseong.hwang2015-03-242-33/+0
| | | | | | | | BUG=443151 Review URL: https://codereview.chromium.org/1027823003 Cr-Commit-Position: refs/heads/master@{#321952}
* Mapping all newly available ES3 entry points in webgraphicscontext3d_implbajones2015-03-242-59/+99
| | | | | | | | BUG=295792 Review URL: https://codereview.chromium.org/1025303006 Cr-Commit-Position: refs/heads/master@{#321941}
* Add backslashes to "Adreno (TM) 3xx" canvas/ganesh whitelist entry.aelias2015-03-241-2/+2
| | | | | | | | | | | | | | This entry didn't match because the parens were interpreted as regexp grouping instead of literal characters. I didn't notice the problem before given that K+ Adreno 3xx devices are also covered by the OpenGL ES 3.0 policy. This should actually expand the Ganesh whitelist to all pre-K Adreno 3xx devices as originally intended by r307526. BUG=467581,424970 Review URL: https://codereview.chromium.org/1025803003 Cr-Commit-Position: refs/heads/master@{#321910}
generated by cgit v1.1 at 2025-02-15 15:47:39 +0000