summaryrefslogtreecommitdiffstats
path: root/content/browser/gpu/compositor_util.cc
Commit message (Collapse)AuthorAgeFilesLines
* content: Disable impl-side painting on MacOS.reveman@chromium.org2014-05-021-0/+4
| | | | | | | | BUG=169282 Review URL: https://codereview.chromium.org/267723005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267775 0039d316-1c4b-4281-b951-d872f2087c98
* Turn on impl-side painting when --enable-bleeding-edge-rendering-fast-paths ↵chrishtr@chromium.org2014-04-301-0/+3
| | | | | | | | | | is true. BUG=364934 Review URL: https://codereview.chromium.org/253153002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267089 0039d316-1c4b-4281-b951-d872f2087c98
* Re-land: cc: Enable impl-side painting by default on all platforms where ↵reveman@chromium.org2014-04-281-5/+1
| | | | | | | | | | threaded compositing is used. BUG=169282 Review URL: https://codereview.chromium.org/242803007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266654 0039d316-1c4b-4281-b951-d872f2087c98
* Fix for pinch virtual viewport flag wasn't fully enabled.bokan@chromium.org2014-04-281-0/+16
| | | | | | | | | | Missed a case when enabling the flag on CrOS in r266119. BUG=367099 Review URL: https://codereview.chromium.org/257903002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266504 0039d316-1c4b-4281-b951-d872f2087c98
* content: Fix about:gpu "Rasterization" status field.reveman@chromium.org2014-04-281-7/+11
| | | | | | | | | | | This makes the "Rasterization" field work properly again and adds some constants to prevent this from breaking again. BUG=367124 Review URL: https://codereview.chromium.org/250773007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266503 0039d316-1c4b-4281-b951-d872f2087c98
* Revert of cc: Enable impl-side painting by default on all platforms where ↵pfeldman@chromium.org2014-04-281-1/+5
| | | | | | | | | | | | | | | | | | | | | | | threaded compositing is used. (https://codereview.chromium.org/242803007/) Reason for revert: This makes DevTools unusable on Linux Aura, see crbug.com/367673. Original issue's description: > cc: Enable impl-side painting by default on all platforms where threaded compositing is used. > > BUG=169282 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=266471 TBR=piman@chromium.org,vangelis@chromium.org,enne@chromium.org,reveman@chromium.org NOTREECHECKS=true NOTRY=true BUG=169282 Review URL: https://codereview.chromium.org/259843006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266499 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Enable impl-side painting by default on all platforms where threaded ↵reveman@chromium.org2014-04-281-5/+1
| | | | | | | | | | compositing is used. BUG=169282 Review URL: https://codereview.chromium.org/242803007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266471 0039d316-1c4b-4281-b951-d872f2087c98
* Remove --disable-accelerated-video and GPU_FEATURE_TYPE_ACCELERATED_VIDEOpiman@chromium.org2014-04-261-9/+0
| | | | | | | | | | | | These are just compositing triggers. GPU_FEATURE_TYPE_ACCELERATED_VIDEO is completely ignored, and there's no reason to disable the compositing trigger since FCM is always on in production. BUG=362164 Review URL: https://codereview.chromium.org/240253006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266354 0039d316-1c4b-4281-b951-d872f2087c98
* Remove GPU_FEATURE_TYPE_3D_CSS and --disable-accelerated-layerspiman@chromium.org2014-04-251-24/+2
| | | | | | | | | | | | | | | | | | We ignore GPU_FEATURE_TYPE_3D_CSS, so remove it. Nothing sets --disable-accelerated-layers, and it doesn't correspond to a production path, so remove it. This lets us clean up some WebPreferences fields which are always set to true. Also remove WebPreferences::accelerated_compositing_for_plugins_enabled which is always true. BUG=362164,365847 R=bbudge@chromium.org, danakj@chromium.org, tsepez@chromium.org Review URL: https://codereview.chromium.org/239973005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266226 0039d316-1c4b-4281-b951-d872f2087c98
* Enable GPU rasterization by default on Androidajuma@chromium.org2014-04-181-7/+1
| | | | | | | | | | This enables hybrid GPU rasterization on Android. BUG=362779 Review URL: https://codereview.chromium.org/241223004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264735 0039d316-1c4b-4281-b951-d872f2087c98
* Remove FCM from about:gpu and improve the Compositing field output.danakj@chromium.org2014-04-181-20/+7
| | | | | | | | | | | | | | | The compositing field should show if hardware or software compositing is being used, and if the thread is being used in either case. ForceCompositingMode doesn't exist anymore (it's always on) so just remove it from the page. R=piman@chromium.org, zmo@chromium.org BUG=363772 Review URL: https://codereview.chromium.org/238043006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264709 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the --force-compositing-mode flag except for LayoutTests.danakj@chromium.org2014-04-171-45/+2
| | | | | | | | | | | | | | Stop honoring the flag and remove IsForceCompositingEnabled from content/. Now only WebkitTestRunner checks for the presence of the flag. R=piman@chromium.org, miu@chromium.org, darin@chromium.org TBR=darin BUG=363772 Review URL: https://codereview.chromium.org/240183005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264646 0039d316-1c4b-4281-b951-d872f2087c98
* Change ACCELERATED_COMPOSITING blacklist to GPU_COMPOSITING.danakj@chromium.org2014-04-171-14/+7
| | | | | | | | | | | | | | | | Remove any checks for ACCELERATED_COMPOSITING to determine if compositing is available, since it always is. Instead rename the blacklist entry to GPU_COMPOSITING and use it to prevent GL-based compositing. Depends on: https://codereview.chromium.org/238933009/ R=jbauman@chromium.org, piman@chromium.org, zmo@chromium.org BUG=363772 Review URL: https://codereview.chromium.org/239083006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264566 0039d316-1c4b-4281-b951-d872f2087c98
* Add GPU_RASTERIZATION as one of the gpu blacklist features.zmo@chromium.org2014-04-171-4/+18
| | | | | | | | | | BUG=362782 TEST=gpu_unittests R=ajuma@chromium.org, kbr@chromium.org Review URL: https://codereview.chromium.org/240243005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264564 0039d316-1c4b-4281-b951-d872f2087c98
* Remove --disable-accelerated-compositingpiman@chromium.org2014-04-161-12/+4
| | | | | | | | | | | | | | After r264075, this is not used by the renderer. Also, nothing sets it but tests (and for the wrong reasons). Also, it's not like it works any more after r264103. Replace it in tests by --disable-gpu, and remove from the code. BUG=362164 R=danakj@chromium.org, kbr@chromium.org, shess@chromium.org Review URL: https://codereview.chromium.org/238933009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264295 0039d316-1c4b-4281-b951-d872f2087c98
* Remove ForceCompositingMode from the GPU blacklist.danakj@chromium.org2014-04-161-11/+2
| | | | | | | | | | | | This mode is always on for everything we ship, so we never need to blacklist it. R=jbauman@chromium.org BUG=363772 Review URL: https://codereview.chromium.org/239253005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264263 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 263998 "PCI scan to find GPU: not limited to just VGA."zmo@chromium.org2014-04-151-10/+1
| | | | | | | | | | | | | | | | | | | | | Accidentally commited something unrelated to this CL. > PCI scan to find GPU: not limited to just VGA. > > On Thinkpad T430s with NVIDIA Optimus, the NVIDIA GPU is listed as a > 3D controller, not a VGA compatible controller. > > BUG=363418 > TEST= > R=kbr@chromium.org > > Review URL: https://codereview.chromium.org/237673004 TBR=zmo@chromium.org Review URL: https://codereview.chromium.org/239453004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264023 0039d316-1c4b-4281-b951-d872f2087c98
* PCI scan to find GPU: not limited to just VGA.zmo@chromium.org2014-04-151-1/+10
| | | | | | | | | | | | | On Thinkpad T430s with NVIDIA Optimus, the NVIDIA GPU is listed as a 3D controller, not a VGA compatible controller. BUG=363418 TEST= R=kbr@chromium.org Review URL: https://codereview.chromium.org/237673004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@263998 0039d316-1c4b-4281-b951-d872f2087c98
* Remove --disable-force-compositing-mode flag and about:flags entrypiman@chromium.org2014-04-121-4/+1
| | | | | | | | | | | | Tests that were setting it were cleaned up in https://codereview.chromium.org/137663006/. It's not a path we want to support. BUG=None Review URL: https://codereview.chromium.org/234423003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@263534 0039d316-1c4b-4281-b951-d872f2087c98
* content: Restore rasterization status in about:gpu.reveman@chromium.org2014-03-311-5/+36
| | | | | | | | | | | | | | | | | | | | Without any flags it shows: Rasterization: Software only. Hardware acceleration disabled. Add --enable-impl-side-painting and it shows: Rasterization: Software only, multi-threaded Add --enable-gpu-rasterization and it shows: Rasterization: Hardware accelerated add --force-gpu-rasterization and it shows: Rasterization: Hardware accelerated on all pages BUG=354449 Review URL: https://codereview.chromium.org/210483002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@260623 0039d316-1c4b-4281-b951-d872f2087c98
* Fix "unreachable code" warnings (MSVC warning 4702) in content/.pkasting@chromium.org2014-03-191-18/+7
| | | | | | | | | | BUG=346399 TEST=none R=jam@chromium.org Review URL: https://codereview.chromium.org/202863004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@258096 0039d316-1c4b-4281-b951-d872f2087c98
* Define a --force-gpu-rasterization flagajuma@chromium.org2014-03-111-4/+17
| | | | | | | | | | | | | | | This flag forces gpu rasterization for all layers (that is, it behaves the way --enable-gpu-rasterization behaved previously). --enable-gpu-rasterization now enables gpu rasterization only on layers that have a GPU rasterization hint. Since this hint will be added in a later CL, this flag is currently a no-op. BUG=329722 Review URL: https://codereview.chromium.org/189883009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@256143 0039d316-1c4b-4281-b951-d872f2087c98
* List gpu driver bug workaround reasons in about:gpuzmo@chromium.org2014-02-211-0/+8
| | | | | | | | | | | | Before we only list information on why we disable a feature. It helps to also list information on why we apply a driver bug workaround. BUG=330785 TEST=about:gpu R=kbr@chromium.org, nduca@chromium.org Review URL: https://codereview.chromium.org/171453003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252440 0039d316-1c4b-4281-b951-d872f2087c98
* Remove options to disable deadline schedulingbrianderson@chromium.org2014-02-201-13/+0
| | | | | | | | BUG=344090 Review URL: https://codereview.chromium.org/164373012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252260 0039d316-1c4b-4281-b951-d872f2087c98
* Move multisampling control from gpu blacklist to driver bug workaround list.zmo@chromium.org2014-02-151-8/+0
| | | | | | | | | BUG=330785 TEST=bots Review URL: https://codereview.chromium.org/135273002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251591 0039d316-1c4b-4281-b951-d872f2087c98
* Fix GPU feature enumeration in GetGpuFeatureInfo.primiano@chromium.org2014-02-111-10/+9
| | | | | | | | | | | The current logic of GetGpuFeatureInfo for listing GPU features is broken. See the related bug for more details. BUG=342461 Review URL: https://codereview.chromium.org/158893006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250277 0039d316-1c4b-4281-b951-d872f2087c98
* Remove Windows accelerated surface support.jbauman@chromium.org2014-01-271-8/+0
| | | | | | | | | | Presentation now only happens directly from the GPU process, so this code isn't used anymore. BUG=325947 Review URL: https://codereview.chromium.org/140173004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@247312 0039d316-1c4b-4281-b951-d872f2087c98
* Enable software compositing on Macccameron@chromium.org2013-12-181-5/+6
| | | | | | | | | | | | | | Disable accelerated compositing test to match Aura behavior. Change task manager tests to disable the GPU instead of turning off accelerated compositing (as this doesn't have meaning in the software composited world). BUG=286038 Review URL: https://codereview.chromium.org/102333003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@241511 0039d316-1c4b-4281-b951-d872f2087c98
* AndroidVideoEncodeAccelerator is born!fischman@chromium.org2013-12-041-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | AVEA is the encode-side analogue of AndroidVideoDecodeAccelerator, or the Android analogue of ExynosVideoEncodeAccelerator, depending on your POV. Also included in this CL: - MediaCodecBridge learns how to be an encoder, too. - MediaCodecBridge::Start is sunk into Create since they were always called together. - android.os.Log() is given an exception parameter instead of concatenating its .toString() (and losing its stacktrace!) - MediaCodecBridge exposes its buffers to reduce unnecessary memcpy'ing Performance impact: isolating encode performance by making Android decode only 240p and no audio send/receive with the following URLs: z620/gprecise: https://apprtc.appspot.com/?video=maxHeight=240&audio=false&r=<ROOM> Nexus5: https://apprtc.appspot.com/?video=minHeight=720,maxHeight=720,minWidth=1280,maxWidth=1280&audio=false&r=<ROOM> All 4 cores are max'd are running at top speed (ondemand governor ramps them up on its own with this workload). SW encode: CPU utilization 80% and desktop receives 0.1-0.5FPS (jankily). HW encode: CPU utilization 60-70% and desktop receives 30FPS reliably. Comparing an easier workload of encoding 360p: z620/gprecise: https://apprtc.appspot.com/?video=maxHeight=240&audio=false&r=<ROOM> Nexus5: https://apprtc.appspot.com/?video=minHeight=360,maxHeight=360,minWidth=640,maxWidth=640&audio=false&r=<ROOM> Set all 4 cores to "performance" governor for stable comparison. SW encode: CPU utilization 63% and desktop receives 30FPS reliably. HW encode: CPU utilization 53% and desktop receives 30FPS reliably. BUG=313115 Review URL: https://codereview.chromium.org/74563002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238658 0039d316-1c4b-4281-b951-d872f2087c98
* Make consistent with Accelerated 2D Canvas flag on both implementation and ↵dongseong.hwang@intel.com2013-12-031-9/+2
| | | | | | | | | | | | | | chrome://gpu. Currently, we don't enable accelerated 2d canvas in software rendering mode, but chrome://gpu does not concern software rendering mode. This CL adds GPUInfo::SupportsAccelerated2dCanvas() so that any clients query if accelerated 2d canvas is supported. Review URL: https://codereview.chromium.org/95013004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238347 0039d316-1c4b-4281-b951-d872f2087c98
* Merge gpu_switching_list into gpu_driver_bug_list.zmo@chromium.org2013-11-051-19/+0
| | | | | | | | | | BUG=314901 TEST=gpu_unittests R=bajones@chromium.org, kbr@chromium.org, piman@chromium.org, sievers@chromium.org Review URL: https://codereview.chromium.org/57633007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233143 0039d316-1c4b-4281-b951-d872f2087c98
* Enable the threaded-compositing command line switches even under Aura.dpranke@chromium.org2013-11-021-5/+5
| | | | | | | | | | | | Previously we had an #ifdef AURA that was overriding things and would break running the layout tests under Aura. R=jamesr@chromium.org, piman@chromium.org BUG=229207, 233830 Review URL: https://codereview.chromium.org/56243004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232546 0039d316-1c4b-4281-b951-d872f2087c98
* Enable delegated renderer on Chrome OS toopiman@chromium.org2013-10-311-3/+2
| | | | | | | | BUG=123444 Review URL: https://codereview.chromium.org/50263002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232006 0039d316-1c4b-4281-b951-d872f2087c98
* Statically enable TCM and get rid of compositing-mode-field-trials.gab@chromium.org2013-10-301-17/+13
| | | | | | | | | | | | | This is based on top of https://codereview.chromium.org/27197009/ BUG=302738, 233830, 306557 Originally Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=229806 Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=229907 Review URL: https://codereview.chromium.org/26389003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@231949 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 229806 "Statically enable TCM and get rid of compositing-..."alecflett@chromium.org2013-10-211-13/+17
| | | | | | | | | | | | | | | | | > Statically enable TCM and get rid of compositing-mode-field-trials. > > This is based on top of https://codereview.chromium.org/27197009/ > > TBR=joi > BUG=302738, 233830, 306557 > > Review URL: https://codereview.chromium.org/26389003 TBR=gab@chromium.org Review URL: https://codereview.chromium.org/33663002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@229907 0039d316-1c4b-4281-b951-d872f2087c98
* Statically enable TCM and get rid of compositing-mode-field-trials.gab@chromium.org2013-10-211-17/+13
| | | | | | | | | | | This is based on top of https://codereview.chromium.org/27197009/ TBR=joi BUG=302738, 233830, 306557 Review URL: https://codereview.chromium.org/26389003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@229806 0039d316-1c4b-4281-b951-d872f2087c98
* Enforce FCM settings via the blacklist rather than in-code version checks.gab@chromium.org2013-10-181-12/+6
| | | | | | | | | | | | | | | | As of http://crrev.com/228816 both Win and Mac bots are properly using the blacklist and version checks in compositor_util.cc are no longer required. Also cleanup the blacklist to: 1) Put Vista and XP blacklisting of FCM under the same rule. 2) Always blacklist Stage3D when FCM is disabled (as in https://codereview.chromium.org/25602002). This is part of https://codereview.chromium.org/22198004/ which was split out into smaller chunks (now a follow-up to https://codereview.chromium.org/23703017/). BUG=302738, 233830, 306557 Review URL: https://codereview.chromium.org/27197009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@229309 0039d316-1c4b-4281-b951-d872f2087c98
* [telemetry] Print graphics feature status.dtu@chromium.org2013-10-161-3/+294
| | | | | | | | | | | | Moved GetFeatureStatus() from the gpu_internals_ui to compositor_util, so we can add it to the existing SystemInfo.getInfo API. This exposes the top three sections of the chrome://gpu page through DevTools to Telemetry. BUG=296773 TEST=TBD Review URL: https://codereview.chromium.org/24828002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228870 0039d316-1c4b-4281-b951-d872f2087c98
* flags: Enable deadline scheduling by default on all platformspiman@chromium.org2013-10-161-2/+2
| | | | | | | | | | | | This is a test to see if there is anything unknown related to the deadline scheduler that needs to be addressed. BUG=305226 R=piman@chromium.org Review URL: https://codereview.chromium.org/26735004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228808 0039d316-1c4b-4281-b951-d872f2087c98
* Enable delegated rendering on Aura Windows and Linux (not Chrome OS)piman@chromium.org2013-10-111-0/+6
| | | | | | | | BUG=123444 Review URL: https://codereview.chromium.org/26853004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228225 0039d316-1c4b-4281-b951-d872f2087c98
* Add deadline scheduling flags and keep disabled by default everywherebrianderson@chromium.org2013-09-211-0/+13
| | | | | | | | | | | | | | | | | | The following command line flags override the default values for the Renderer on both Android and Aura: --enable-deadline-scheduling --disable-deadline-scheduling The following command line flags override the default values for the Browser on Aura: --enable-ui-deadline-scheduling --disable-ui-deadline-scheduling BUG=243461 Review URL: https://chromiumcodereview.appspot.com/23587028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224584 0039d316-1c4b-4281-b951-d872f2087c98
* Re-enable blacklist check for force_compositing_mode..!gab@chromium.org2013-09-201-2/+7
| | | | | | | | | | | | | Oops, I made a HUGE mistake and somehow removed that check in https://chromiumcodereview.appspot.com/23874016/ (at the time IIRC I refactored this because I thought it was redudant with the blacklist check in CanDoAcceleratedCompositing... it clearly isn't since it's not checking the same blacklist item... no idea how that slipped through... my bad). BUG=286540 TBR=zmo@chromium.org NOTRY=True Review URL: https://chromiumcodereview.appspot.com/24152012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224456 0039d316-1c4b-4281-b951-d872f2087c98
* Always enable FCM on Mac 10.8.gab@chromium.org2013-09-191-16/+12
| | | | | | | | | | | | This is the Mac equivalent of Windows' http://crrev.com/221643. This needs to land before https://codereview.chromium.org/23514071/. BUG=286540 Review URL: https://chromiumcodereview.appspot.com/23447045 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224037 0039d316-1c4b-4281-b951-d872f2087c98
* Always enable FCM if threaded compositing is on.gab@chromium.org2013-09-191-4/+3
| | | | | | | | BUG=It was otherwise previously possible to have threaded compositing yet not FCM... (e.g., by passing --enable-threaded-compositing without passing --force-compositing-mode). Review URL: https://chromiumcodereview.appspot.com/24195014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224016 0039d316-1c4b-4281-b951-d872f2087c98
* Disable delegated renderingpiman@chromium.org2013-09-181-5/+0
| | | | | | | | | BUG=None R=danakj@chromium.org Review URL: https://codereview.chromium.org/23537058 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223757 0039d316-1c4b-4281-b951-d872f2087c98
* Always enable FCM on Windows Vista+.gab@chromium.org2013-09-061-18/+23
| | | | | | | | | | | | | | | This is part 2/3 of re-landing https://codereview.chromium.org/22198004/. It will land before part 1/3 @ https://codereview.chromium.org/23534006 because this part is core to getting Aura on the waterfall and part 1/3 has already been blocking us for too long. We want to use the blacklist rather than hardcode OS versions in compositor_util, but for now hardcoding is fine... TBR=zmo BUG=233830, 267038 Review URL: https://chromiumcodereview.appspot.com/23874016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221643 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 221114 "Enable GPU blacklist in tests."gab@chromium.org2013-09-041-7/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > Enable GPU blacklist in tests. > > Partial re-land of https://codereview.chromium.org/22198004/) -- Always enable FCM on Windows -- Part 1/3. > > On top of fixing some of the issues there; only lands the part that enables the GPU blacklist in tests as the former CL is too hard to land all at once. > > Also keeping --skip-gpu-data-loading around for now to be able to deal with failures caused in layout_tests by this on their own later (this needs to land ASAP and layout_tests don't need this ASAP). > > Another CL will follow to always enable FCM on non-blacklisted Windows machines. > > This part re-enables loading the blacklist in tests (and adds a content_browsertest to make sure that the configuration we expect to be testing is indeed the one we are testing -- this uncertainty is basically the only reason the blacklist was explicitly disabled before). > > This CL also cleans up compositor_util.cc which was enforcing the blacklist twice. > > The original plan was to do this only for Windows as Mac/Linux was causing trouble, but it turns out to be harder to do it only on Windows; so taking care of http://crbug.com/277242 in this CL too after all... > > BUG=233830, 267038, 190942, 277242 > TBR=jcivelli, piman > > Originally Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=219132 > Then Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=219159 > > Review URL: https://chromiumcodereview.appspot.com/23534006 TBR=gab@chromium.org Review URL: https://codereview.chromium.org/23775004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221145 0039d316-1c4b-4281-b951-d872f2087c98
* Enable GPU blacklist in tests.gab@chromium.org2013-09-041-18/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | Partial re-land of https://codereview.chromium.org/22198004/) -- Always enable FCM on Windows -- Part 1/3. On top of fixing some of the issues there; only lands the part that enables the GPU blacklist in tests as the former CL is too hard to land all at once. Also keeping --skip-gpu-data-loading around for now to be able to deal with failures caused in layout_tests by this on their own later (this needs to land ASAP and layout_tests don't need this ASAP). Another CL will follow to always enable FCM on non-blacklisted Windows machines. This part re-enables loading the blacklist in tests (and adds a content_browsertest to make sure that the configuration we expect to be testing is indeed the one we are testing -- this uncertainty is basically the only reason the blacklist was explicitly disabled before). This CL also cleans up compositor_util.cc which was enforcing the blacklist twice. The original plan was to do this only for Windows as Mac/Linux was causing trouble, but it turns out to be harder to do it only on Windows; so taking care of http://crbug.com/277242 in this CL too after all... BUG=233830, 267038, 190942, 277242 TBR=jcivelli, piman Originally Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=219132 Then Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=219159 Review URL: https://chromiumcodereview.appspot.com/23534006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221114 0039d316-1c4b-4281-b951-d872f2087c98
* Force delegated renderer on Aurapiman@chromium.org2013-08-301-0/+24
| | | | | | | | BUG=123444 Review URL: https://chromiumcodereview.appspot.com/22797008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220638 0039d316-1c4b-4281-b951-d872f2087c98
* Always FCM+compositor thread on all Aura platformspiman@chromium.org2013-08-291-15/+4
| | | | | | | | | | | It's already on for Windows and Chrome OS, and there's no reason to leave it off on Linux. It's also a prerequisite for Übercompositor BUG=123444 Review URL: https://chromiumcodereview.appspot.com/23672002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220189 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-28 10:37:19 +0000