summaryrefslogtreecommitdiffstats
path: root/content/gpu
Commit message (Collapse)AuthorAgeFilesLines
* Blacklist accelerated canvas on Android Adreno chipsets.aelias@chromium.org2012-11-191-1/+39
| | | | | | | | | | As this is the first Android blacklist entry, add Android support to the blacklist parser. Also add new code to extract the version number we're interested in. BUG=161575 Review URL: https://chromiumcodereview.appspot.com/10764014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168620 0039d316-1c4b-4281-b951-d872f2087c98
* Stop watchdog thread before sandbox initialization.zmo@chromium.org2012-11-151-0/+4
| | | | | | | | | | Then Start it again after sandbox is up. BUG=132893 TEST=no sandbox error message Review URL: https://codereview.chromium.org/11275337 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167995 0039d316-1c4b-4281-b951-d872f2087c98
* Remove calling into CGLQueryRendererInfo to decide dual gpu supporting.zmo@google.com2012-11-143-0/+3
| | | | | | | | | | | | We use the GPU numbers collected through IOKit to make the decision instead. Also, clean the gpu_info_ in GPU process before calling into GPU collection, otherwise we will see integrated GPU gets accumulated incorrectly in each collection. BUG=155938 TEST=bot, mac with dual GPUs Review URL: https://codereview.chromium.org/11358225 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167767 0039d316-1c4b-4281-b951-d872f2087c98
* Enable GPU watchdog after initializing GL on Chrome OSjbauman@chromium.org2012-11-081-1/+14
| | | | | | | | | | | This was causing errors when developers switched to VT2 on startup. BUG=159137 Review URL: https://chromiumcodereview.appspot.com/11293158 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166590 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: add option to link libpci directly instead of using dlopen.phajdan.jr@chromium.org2012-11-011-49/+34
| | | | | | | | | | | | | This is for Linux distros, so they can detect more breakages at compile time and using automated tools. BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/11343015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165482 0039d316-1c4b-4281-b951-d872f2087c98
* Set can_lose_context to false for Chrome OS.marcheu@chromium.org2012-11-011-0/+4
| | | | | | | | | | | | | | | This allows us to use 2D accelerated canvas on EGL and Chrome OS, where it was previously disabled. BUG=chromium-os:34278 TEST=check that accelerated canvas is enabled, try canvas 2D apps like fishie tank and entanglement, notice it's faster. Change-Id: I3b3616095967979f0cbeb52e16b749dc4f919f6f Review URL: https://chromiumcodereview.appspot.com/11367027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165473 0039d316-1c4b-4281-b951-d872f2087c98
* Collect machine model info in gpu_info_collector and expose it to about:gpu.zmo@chromium.org2012-10-281-0/+11
| | | | | | | | | BUG=158147 TEST=content_unittests, about:gpu page on Mac(manual) Review URL: https://chromiumcodereview.appspot.com/11311021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@164571 0039d316-1c4b-4281-b951-d872f2087c98
* Cause GPU hangs on Windows to make crash dumps.jbauman@chromium.org2012-10-261-1/+8
| | | | | | | | | | | This should help us debug any hangs that happen on startup. BUG= Review URL: https://chromiumcodereview.appspot.com/11333002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@164416 0039d316-1c4b-4281-b951-d872f2087c98
* Initialize GPU watchdog before initializing GPU implementation.jbauman@chromium.org2012-10-253-44/+62
| | | | | | | | | | | Initializing the GPU driver could hang, so start the watchdog beforehand. 10s to initialize the GPU driver shouldn't be too low. BUG=144221 Review URL: https://chromiumcodereview.appspot.com/11192029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@164075 0039d316-1c4b-4281-b951-d872f2087c98
* Move a bunch of code in content\common (as well as a few left in renderer) ↵jam@chromium.org2012-10-227-18/+40
| | | | | | | | to the content namespace. Review URL: https://codereview.chromium.org/11227033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@163359 0039d316-1c4b-4281-b951-d872f2087c98
* Add flag to crash GPU process on hang.jbauman@chromium.org2012-10-181-2/+9
| | | | | | | | | | | Chromium developers should be able to try and use this flag to cause crash reports and see what's causing hangs. BUG= Review URL: https://chromiumcodereview.appspot.com/11191020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162792 0039d316-1c4b-4281-b951-d872f2087c98
* Figure out whether we have enough information to make the final GPU ↵zmo@chromium.org2012-10-091-21/+6
| | | | | | | | | | | | blacklisting decision. If yes and all GPU features are blacklisted, we don't launch GPU process. BUG=154130 TEST=content_unittests Review URL: https://codereview.chromium.org/11047011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160923 0039d316-1c4b-4281-b951-d872f2087c98
* gl: Move GpuSwitchingManager into ui namespace.tfarina@chromium.org2012-10-081-2/+2
| | | | | | | | | BUG=127983 TBR=apatrick@chromium.org Review URL: https://codereview.chromium.org/11013008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160728 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 160526 - Crash GPU process on watchdog timeout.vangelis@google.com2012-10-081-2/+2
| | | | | | | | | | | | | | | We can temporarily do this to see what the causes of GPU hangs are. BUG=144221 Review URL: https://chromiumcodereview.appspot.com/10986079 TBR=jbauman@chromium.org Review URL: https://codereview.chromium.org/11066057 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160662 0039d316-1c4b-4281-b951-d872f2087c98
* Crash GPU process on watchdog timeout.jbauman@chromium.org2012-10-061-2/+2
| | | | | | | | | | | | We can temporarily do this to see what the causes of GPU hangs are. BUG=144221 Review URL: https://chromiumcodereview.appspot.com/10986079 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160526 0039d316-1c4b-4281-b951-d872f2087c98
* Make about:gpu page reflects the current GPU in real time.zmo@google.com2012-10-042-6/+5
| | | | | | | | | | This is for Mac with dual GPUs, dynamic switching enabled. BUG= TEST=manually on the affected macs Review URL: https://codereview.chromium.org/11039033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160170 0039d316-1c4b-4281-b951-d872f2087c98
* Delete some unused code found by -Wunused-functionthakis@chromium.org2012-10-011-0/+6
| | | | | | | | BUG=none,100309 Review URL: https://chromiumcodereview.appspot.com/10977073 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@159592 0039d316-1c4b-4281-b951-d872f2087c98
* Add override message to divide GPU memory among windows.ccameron@chromium.org2012-10-012-0/+9
| | | | | | | | | | | The "number of windows" message is to be sent from the browser process, which is much more reliable than trying to reverse-engineer it from visibility messages asynchronously coming from WebKit. BUG=146448 Review URL: https://chromiumcodereview.appspot.com/11031009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@159591 0039d316-1c4b-4281-b951-d872f2087c98
* Move force_discrete GPU on older MacBookPro models to GpuBlacklistzmo@google.com2012-10-011-1/+2
| | | | | | | | | | | | | | Before we hardwired the forcing. Also, we refactor the SupportsDualGpus() code so it's only checked on browser process, mainly the part we check the availability of online/offline renderers. We suspect calling the renderer detection code at the same time in browser/gpu processes might cause GPU driver crashes on certain Mac systems (mostly 10.8 from crash reports). This refactoring hopefully will fix the issue. BUG=151741,131276 TEST=tree, manual on dual GPU systems (10.7 and 10.8) Review URL: https://codereview.chromium.org/10995002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@159579 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up scoped_com_initializer.h, primarily by removing #ifdefs for ↵pkasting@chromium.org2012-10-011-2/+2
| | | | | | | | | | | | non-Windows. Instead change files that use this to specifically #ifdef it for OS_WIN, like we do most other Windows-specific code. I plan to factor out the "subclass base::Thread to init MTA on Windows" pattern to its own file in a followup change. BUG=none TEST=none Review URL: https://codereview.chromium.org/10990079 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@159545 0039d316-1c4b-4281-b951-d872f2087c98
* Re-enable the GPU watchdog on Windowsjbauman@chromium.org2012-09-261-9/+0
| | | | | | | | | | | | We're seeing a lot of plugin and renderer-process hangs that are probably caused by GPU hangs, so we can try re-enabling the GPU watchdog to prevent them and see what's causing the GPU hangs. BUG=144221 Review URL: https://chromiumcodereview.appspot.com/10993026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158741 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 158211 - Revert 158076 - Implement blacklist's force GPU capability ↵tzik@chromium.org2012-09-231-0/+11
| | | | | | | | | | | | | | | | | | | in dual GPU machines. This is part 2. In part one we implement the semantics in blacklist. Now we hook it up with the "real" forcing code. For now we only hook it up with Mac CGL port. BUG=140114,131276,111720 TEST=tree Review URL: https://codereview.chromium.org/10909221 TBR=zmo@chromium.org Review URL: https://codereview.chromium.org/10959061 TBR=tzik@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158213 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 158076 - Implement blacklist's force GPU capability in dual GPU machines.tzik@chromium.org2012-09-231-11/+0
| | | | | | | | | | | | | | | This is part 2. In part one we implement the semantics in blacklist. Now we hook it up with the "real" forcing code. For now we only hook it up with Mac CGL port. BUG=140114,131276,111720 TEST=tree Review URL: https://codereview.chromium.org/10909221 TBR=zmo@chromium.org Review URL: https://codereview.chromium.org/10959061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158211 0039d316-1c4b-4281-b951-d872f2087c98
* Implement blacklist's force GPU capability in dual GPU machines.zmo@chromium.org2012-09-211-0/+11
| | | | | | | | | | | | This is part 2. In part one we implement the semantics in blacklist. Now we hook it up with the "real" forcing code. For now we only hook it up with Mac CGL port. BUG=140114,131276,111720 TEST=tree Review URL: https://codereview.chromium.org/10909221 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158076 0039d316-1c4b-4281-b951-d872f2087c98
* Show gpu process sandbox status in the about:gpu page.skaslev@google.com2012-09-111-2/+4
| | | | | | | | | BUG=144663 R=nduca@chromium.org,jln@chromium.org,piman@chromium.org,estade@chromium.org Review URL: https://chromiumcodereview.appspot.com/10915189 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156146 0039d316-1c4b-4281-b951-d872f2087c98
* Count all systems with an AMD driver and Intel GPU PCI ID as AMD switchablejbauman@chromium.org2012-09-061-3/+6
| | | | | | | | | | | | Apparently some of these weren't reporting as switchable, which was causing problems. BUG=146695 Review URL: https://chromiumcodereview.appspot.com/10928014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155272 0039d316-1c4b-4281-b951-d872f2087c98
* Fix a typo in gpu_info_collector_linux.cc.simonmorris@chromium.org2012-09-051-1/+1
| | | | | | Review URL: https://chromiumcodereview.appspot.com/10908075 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154894 0039d316-1c4b-4281-b951-d872f2087c98
* GPU process sends IPC to browser process indicating success of initialization.apatrick@chromium.org2012-08-241-0/+2
| | | | | | | | | | This is used for a histogram to measure the proportion of normal GPU process terminations that are caused by failure to initialize. BUG=142797 Review URL: https://chromiumcodereview.appspot.com/10872051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153142 0039d316-1c4b-4281-b951-d872f2087c98
* GPU: warm-up Nvidia driver on Linux for Optimus cards.jln@chromium.org2012-08-231-3/+5
| | | | | | | | | | BUG=140022 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/10879024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152898 0039d316-1c4b-4281-b951-d872f2087c98
* Make optimus GPU detection more robust on Linux.zmo@chromium.org2012-08-221-0/+12
| | | | | | | | | | Sometimes PCI scan fails to identify both Intel/NVIDIA GPUs, but if we identify the Intel GPU, and the NVIDIA driver, then we can safely claim it's a Intel/NVIDIA dual-GPU situatio. BUG=140022 TEST= Review URL: https://chromiumcodereview.appspot.com/10876022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152863 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 152469 - win: Make GPU process crash on exit once it has successfully ↵apatrick@chromium.org2012-08-211-10/+0
| | | | | | | | | | | | | initialized. This is to find out if the GPU process exits after initialization for any other reason. Review URL: https://chromiumcodereview.appspot.com/10864002 TBR=apatrick@chromium.org Review URL: https://chromiumcodereview.appspot.com/10831411 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152596 0039d316-1c4b-4281-b951-d872f2087c98
* win: Make GPU process crash on exit once it has successfully initialized.apatrick@chromium.org2012-08-211-0/+10
| | | | | | | | This is to find out if the GPU process exits after initialization for any other reason. Review URL: https://chromiumcodereview.appspot.com/10864002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152469 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 152040 - GPU process exits with error code on failure to initialize.apatrick@chromium.org2012-08-201-7/+2
| | | | | | | | | | | I think exiting with no error is counted as a GPU process crash for crash stats purposes. Review URL: https://chromiumcodereview.appspot.com/10823375 TBR=apatrick@chromium.org Review URL: https://chromiumcodereview.appspot.com/10854235 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152380 0039d316-1c4b-4281-b951-d872f2087c98
* Add GPU memory tab to the task manager.ccameron@chromium.org2012-08-182-0/+11
| | | | | | | | | | | | | | | | Each renderer process will have all of the resources that the GPU process has allocated on its behalf (including WebGL resources, compositor resources, and the backbuffer) included in its printed total. The GPU process will have the all resources currently allocated by the GPU process in its column. This will be approximately the sum of all other rows. The row for the GPU process is printed in ()s to draw attention to the fact that its size includes duplicates from other processes' sizes. I happy this UI scheme (having played with a few), but I'd wider feedback. Note that we do not account for swapchains or for backbuffers allocated by the browser process, so those allocations are not counted in the total. BUG=140157 Review URL: https://chromiumcodereview.appspot.com/10854076 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152233 0039d316-1c4b-4281-b951-d872f2087c98
* GPU process exits with error code on failure to initialize.apatrick@chromium.org2012-08-171-2/+7
| | | | | | | | I think exiting with no error is counted as a GPU process crash for crash stats purposes. Review URL: https://chromiumcodereview.appspot.com/10823375 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152040 0039d316-1c4b-4281-b951-d872f2087c98
* Fix WinSAT histograms.dtu@chromium.org2012-08-171-11/+15
| | | | | | | | | | | | | Make sure WinSAT.HasResults runs when the preliminary graphics info is collected on startup. Move the individual score histograms to include all the error cases. BUG=None. Review URL: https://chromiumcodereview.appspot.com/10832278 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152024 0039d316-1c4b-4281-b951-d872f2087c98
* GPU: call CreateGLContext() to warm up the sandbox on Linux.jln@chromium.org2012-08-171-39/+105
| | | | | | | | | | | We refactor the sandbox warmup code in a new WarmUpSandbox() function. We call CreateGLContext() as part of the warm-up for Nvidia drivers. BUG=140214 Review URL: https://chromiumcodereview.appspot.com/10831343 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152012 0039d316-1c4b-4281-b951-d872f2087c98
* Refine WinSAT histogram bounds and rescale so the results are integers.dtu@chromium.org2012-08-071-6/+6
| | | | | | | | | BUG=None. TEST=chrome://histograms on Windows show valid results for the WinSAT histograms. Review URL: https://chromiumcodereview.appspot.com/10828165 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150260 0039d316-1c4b-4281-b951-d872f2087c98
* Only dlopen() OMX/VAAPI libs in the GPU process, and only lazily dlsym() ↵fischman@chromium.org2012-08-041-0/+10
| | | | | | | | | | | | | | their symbols. This reinstates r150007, which was reverted in r150009. TBR=piman@chromium.org BUG=140412 Review URL: https://chromiumcodereview.appspot.com/10827173 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150024 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 150007 - Only dlopen() OMX/VAAPI libs in the GPU process, and only ↵fischman@chromium.org2012-08-041-10/+0
| | | | | | | | | | | | | | | | | | | | lazily dlsym() their symbols. Broke several cros bots: http://build.chromium.org/p/chromium.chromiumos/builders/ChromiumOS%20%28daisy%29/builds/1752/steps/cbuildbot/logs/stdio http://build.chromium.org/p/chromium.chromiumos/builders/ChromiumOS%20%28tegra2%29/builds/8653/steps/cbuildbot/logs/stdio http://build.chromium.org/p/chromium.memory/builders/Chromium%20OS%20ASAN%20Builder/builds/1212/steps/compile/logs/stdio http://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20ChromeOS/builds/38398/steps/compile/logs/stdio BUG=140412 Review URL: https://chromiumcodereview.appspot.com/10829182 TBR=fischman@chromium.org Review URL: https://chromiumcodereview.appspot.com/10836098 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150009 0039d316-1c4b-4281-b951-d872f2087c98
* Only dlopen() OMX/VAAPI libs in the GPU process, and only lazily dlsym() ↵fischman@chromium.org2012-08-041-0/+10
| | | | | | | | | | | their symbols. BUG=140412 Review URL: https://chromiumcodereview.appspot.com/10829182 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150007 0039d316-1c4b-4281-b951-d872f2087c98
* Remove all the chrome exceptions in content's DEPS that were there for ↵jam@chromium.org2012-07-301-2/+0
| | | | | | | | | browser_tests, now that content_browsertests is ready. BUG=90448 Review URL: https://chromiumcodereview.appspot.com/10831073 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148983 0039d316-1c4b-4281-b951-d872f2087c98
* Tweak the way we use the third_party\amd videocard codecpu@chromium.org2012-07-191-1/+1
| | | | | | | | | | | Instead of 'official build', we use 'chrome build' See http://codereview.chromium.org/10790060/ for context BUG=117371 Review URL: https://chromiumcodereview.appspot.com/10806024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147516 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Add env var for GPU process sandbox."jorgelo@chromium.org2012-07-191-8/+0
| | | | | | | | | | | | | Now that we implemented a hook for open(), we don't need the env var anymore. BUG=127664 TEST=Bastion still loads on Chrome OS. Review URL: https://chromiumcodereview.appspot.com/10790061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147385 0039d316-1c4b-4281-b951-d872f2087c98
* Wire the AMD switchable videcard detectioncpu@chromium.org2012-07-182-7/+27
| | | | | | | | | So we don't bucket all AMD cards as crappy. BUG=117371 Review URL: https://chromiumcodereview.appspot.com/10790060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147334 0039d316-1c4b-4281-b951-d872f2087c98
* Move the Windows sandbox to sandbox/winjln@chromium.org2012-07-181-1/+1
| | | | | | | | | | | | | This is a rather large refactor to move the Windows sandbox to the right place. BUG= TEST= NOTRY=true TBR=sky@chromium.org Review URL: https://chromiumcodereview.appspot.com/10689170 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147151 0039d316-1c4b-4281-b951-d872f2087c98
* Emergency revert; rietveld broke; tree brokeerg@google.com2012-07-131-1/+1
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146646 0039d316-1c4b-4281-b951-d872f2087c98
* sandbox/src -> sandbox/win/srcjln@chromium.org2012-07-131-1/+1
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146626 0039d316-1c4b-4281-b951-d872f2087c98
* Remove #pragma once from contentajwong@chromium.org2012-07-114-6/+2
| | | | | | Review URL: https://chromiumcodereview.appspot.com/10696166 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146071 0039d316-1c4b-4281-b951-d872f2087c98
* Add env var for GPU process sandbox.jorgelo@chromium.org2012-07-101-0/+7
| | | | | | | | | | | | | | Since the seccomp filter GPU sandbox blocks access to the file system, we need to set an env var with the config line found in /etc/drirc on Chrome OS. This allows games that use S3TC to work inside the sandbox. BUG=127664 TEST=Bastion works on Chrome OS with '--enable-gpu-sandbox'. Review URL: https://chromiumcodereview.appspot.com/10690116 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145990 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-19 21:53:38 +0000