summaryrefslogtreecommitdiffstats
path: root/content/browser/gpu
Commit message (Collapse)AuthorAgeFilesLines
* Don't try to lock surfaces on TOUCH_UI.backer@chromium.org2011-05-302-9/+9
| | | | | | | | | | | On TOUCH_UI, the window to which we are drawing to cannot be locked (they are backed by GtkFixed, not GtkPreserveWindow), so do not try. BUG="Surface *** cannot be referenced." always logged on TOUCH_UI builds on accelerated content. TEST=Try 3D CSS on a TOUCH_UI build. Above message should not be there. Review URL: http://codereview.chromium.org/7085007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@87231 0039d316-1c4b-4281-b951-d872f2087c98
* Fix gpu acceleration with --in-process-gpu and --single-process modes.sievers@google.com2011-05-274-123/+98
| | | | | | | | | | | | With recent changes that have moved gpu message handling in the browser to the IO thread (and moved the handling of messages between gpu and renderer, that are mediated by the browser, to GpuProcessHost), the routing for such messages was broken when running the gpu thread (rather than process). The new approach is to always instantiate GpuProcessHost (even when running a gpu thread only) and have a real IPC channel between host and gpu thread. This makes the 'in-process' GPU code work similar to what the renderer does when running --single-process. Note that --single-process mode is potentially still a bit fragile with this, since ChildProcess and ChildThread are currently written to only allow a single static instance in one process (it would be better to instantiate GpuProcess and RenderProcess simultaneously), so ambiguous calls to access e.g. the main thread are possible. Review URL: http://codereview.chromium.org/7054005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86958 0039d316-1c4b-4281-b951-d872f2087c98
* Get rid of render_messages.h and web_cache_manager.h. I moved the view ↵jam@chromium.org2011-05-261-2/+1
| | | | | | | | | source message to content since it belongs there now that devtools will be in content. BUG=76697 Review URL: http://codereview.chromium.org/7081001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86925 0039d316-1c4b-4281-b951-d872f2087c98
* Fix OperatingSystemName and OperatingSystemVersion on Macstuartmorgan@chromium.org2011-05-251-14/+1
| | | | | | | | | | | | Prior to this change the posix implementations are used, so the return values are "Darwin" and the Darwin version. BUG=None TEST=None Review URL: http://codereview.chromium.org/7065041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86698 0039d316-1c4b-4281-b951-d872f2087c98
* Virtual destructors should have virtual keyword.hans@chromium.org2011-05-251-1/+1
| | | | | | | | | | | | | | | | | Make sure user-declared virtual destructors always have the virtual keyword. The Clang style-check plugin will check for this soon. No functionality change: virtual is only added to destructors that are already implicitly virtual. Also fix a couple of in-line destructor definitions. BUG=83408 TEST=none Review URL: http://codereview.chromium.org/7064033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86587 0039d316-1c4b-4281-b951-d872f2087c98
* Contributed by junov@chromium.org junov@chromium.org2011-05-243-17/+19
| | | | | | | | | | Turns on the gpu accelerated canvas by default BUG=82017 TEST=none Review URL: http://codereview.chromium.org/7064032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86510 0039d316-1c4b-4281-b951-d872f2087c98
* Restore the gpu blacklist logic.zmo@google.com2011-05-241-0/+6
| | | | | | | | | | | The gpu blacklist is no longer applied due to a regression. I decided not to put this fix together with the rest of gpu blacklist logic regression recovering as this is more urgent and simple to fix. BUG=83639 TEST=gpu blacklist is applied. if a gpu feature should be blacklisted, it will. Review URL: http://codereview.chromium.org/7065012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86370 0039d316-1c4b-4281-b951-d872f2087c98
* Make about:gpu report driver information again.nduca@chromium.org2011-05-192-10/+10
| | | | | | | | | | | | | | | | gpu_data_manager was erroneously setting the finalized bit on gpu_info, preventing new information about the driver from being merged into the active GpuInfo state. This is not needed. gpu_data_manager was not running the GpuInfoChanged callbacks when the gpu info changed. This prevented about:gpu from seeing the new gpu strings when they are collected. BUG=83149 Review URL: http://codereview.chromium.org/7049022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85976 0039d316-1c4b-4281-b951-d872f2087c98
* Drive compositor scheduling with the swapbuffers callback.nduca@chromium.org2011-05-121-0/+3
| | | | | | | | | | | | | | This modifies the compositor to hold DoDeferredUpdate until the previous frames are ack'd by the GPU. This vastly improves rendering smoothness. There is some complexity in the way we intercept the SwapBuffers callback due to the different types of GraphicsContexts that get scheduled by render_widget. BUG=80480,53051 Review URL: http://codereview.chromium.org/6902106 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85186 0039d316-1c4b-4281-b951-d872f2087c98
* Only block the GPu process if WebGL, compositing or canvas2D are blacklisted ↵vangelis@chromium.org2011-05-111-1/+9
| | | | | | | | | | (but not if multisampling is blacklisted). This allows us to run on Mac's with AMD h/w. BUG=82104 Review URL: http://codereview.chromium.org/7013002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85031 0039d316-1c4b-4281-b951-d872f2087c98
* Merge gpu_trace_event back into base/debug/trace_event.scheib@chromium.org2011-05-102-3/+2
| | | | | | | | | | | | | | | | | | | | | | | Initial land attempt at http://codereview.chromium.org/6551019/ gpu_trace_event fork at http://codereview.chromium.org/6691013 - gpu_trace_event renamed to base/debug/trace_event and modified as appropriate for base::debug - Unit Tests implemented for trace_event - gpu_common library removed (was added only for gpu_trace_event) - Existing calls to trace_event suffixed with _ETW to make ETW calls (see decisions and incremental plans at end of 6551019) - GPU trace calls renamed to new calls. - Tracing switch removed from test_shell, as linux log file support removed. BUG=79509 TEST=trace_event_win_unittest and about:gpu Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=84284 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=84486 Review URL: http://codereview.chromium.org/6862002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84739 0039d316-1c4b-4281-b951-d872f2087c98
* iwyu: Use callback_old.h where appropriate, part 1.jhawkins@chromium.org2011-05-102-2/+2
| | | | | | | | | | | BUG=none TEST=none R=thakis@chromium.org Review URL: http://codereview.chromium.org/6985009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84725 0039d316-1c4b-4281-b951-d872f2087c98
* Moved content/browser/gpu_* to content/browser/gpu/.apatrick@chromium.org2011-05-0910-0/+3215
Also added an OWNERS file with myself and kbr. TEST=build locally, try BUG=none Review URL: http://codereview.chromium.org/6931017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84661 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-01 10:39:55 +0000