This change adds the apple software renderer as an option on Chrome/Mac. It's enabled by passing...

ui/gfx/gl/gl_context_cgl.cc

Index: ui/gfx/gl/gl_context_cgl.cc
===================================================================
--- ui/gfx/gl/gl_context_cgl.cc	(revision 113194)
+++ ui/gfx/gl/gl_context_cgl.cc	(working copy)
@@ -4,10 +4,12 @@
 
 #include "ui/gfx/gl/gl_context_cgl.h"
 
+#include <OpenGL/CGLRenderers.h>
 #include <vector>
 
 #include "base/logging.h"
 #include "ui/gfx/gl/gl_bindings.h"
+#include "ui/gfx/gl/gl_implementation.h"
 #include "ui/gfx/gl/gl_surface_cgl.h"
 
 namespace gfx {
@@ -42,6 +44,10 @@
   if (using_offline_renderer) {
     attribs.push_back(kCGLPFAAllowOfflineRenderers);
   }
+  if (GetGLImplementation() == kGLImplementationAppleGL) {
+    attribs.push_back(kCGLPFARendererID);
+    attribs.push_back((CGLPixelFormatAttribute) kCGLRendererGenericFloatID);

[Ken Russell (switch to Gerrit), 2011/12/06 19:23:47]

What are the interactions with (a) the dual-GPU code and (b) the IOSurface
support in the browser? In what environments is this new code path expected to
work (DRT, browser/UI tests, full Chrome)?

[Stephen White, 2011/12/06 19:49:04]

Since this is strictly a software renderer, it shouldn't be affected by the
dual-gpu code, so perhaps it should also skip the kCGLPFAAllowOfflineRenderers
flag above it in that case (not sure).  Is there a test I can run to mock a
dual-GPU mac?  

Regardless, since this new code only executes if --use-gl=apple is passed, I
don't think it will affect existing usage.
It works in DRT and full Chrome, but it's not the default on any of those,
obviously (any more than --use-gl=desktop is on Windows, for example).  Don't
know about browser/ui tests.

[Ken Russell (switch to Gerrit), 2011/12/06 22:49:45]

Sorry, there isn't currently. I don't know how to mock out system level APIs
like these. Presumably we could do this by reimplementing the CGL layer and
using e.g. Mesa as the backend renderer. If you have suggestions on how we can
test this behavior in isolation I would appreciate them. In the interim we can
test on dual-GPU machines running 10.7.x if you can provide the test scenarios.
Sounds reasonable. Was mainly wondering if the test setup would be affected.
Interesting. Good to know that it works with the other IOSurface infrastructure.

+  }
   attribs.push_back((CGLPixelFormatAttribute) 0);
 
   CGLPixelFormatObj format;
@@ -86,16 +92,6 @@
   if (IsCurrent(surface))
     return true;
 
-  if (CGLSetPBuffer(static_cast<CGLContextObj>(context_),
-                    static_cast<CGLPBufferObj>(surface->GetHandle()),
-                    0,
-                    0,
-                    0) != kCGLNoError) {
-    LOG(ERROR) << "Error attaching pbuffer to context.";
-    Destroy();
-    return false;
-  }
-
   if (CGLSetCurrentContext(
       static_cast<CGLContextObj>(context_)) != kCGLNoError) {
     LOG(ERROR) << "Unable to make gl context current.";
@@ -122,7 +118,6 @@
 
   SetCurrent(NULL, NULL);
   CGLSetCurrentContext(NULL);
-  CGLSetPBuffer(static_cast<CGLContextObj>(context_), NULL, 0, 0, 0);
 }
 
 bool GLContextCGL::IsCurrent(GLSurface* surface) {
@@ -136,20 +131,6 @@
   if (!native_context_is_current)
     return false;
 
-  if (surface) {
-    CGLPBufferObj current_surface = NULL;
-    GLenum face;
-    GLint level;
-    GLint screen;
-    CGLGetPBuffer(static_cast<CGLContextObj>(context_),
-                  &current_surface,
-                  &face,
-                  &level,
-                  &screen);
-    if (current_surface != surface->GetHandle())
-      return false;
-  }
-
   return true;
 }