Add a command-line switch --skip-gpu-data-loading.

content/public/common/content_switches.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/public/common/content_switches.h"
 
 namespace switches {
 
 // By default, file:// URIs cannot read other file:// URIs. This is an
 // override for developers who need the old behavior for testing.
@@ skipping 424 matching lines @@
 // and study painting behavior.
 const char kShowPaintRects[]                = "show-paint-rects";
 //
 // TODO(scherkus): remove --simple-data-source when our media resource loading
 // is cleaned up and playback testing completed.
 const char kSimpleDataSource[]              = "simple-data-source";
 
 // Runs the renderer and plugins in the same process as the browser
 const char kSingleProcess[]                 = "single-process";
 
+// Skip gpu info collection, blacklist loading, and blacklist auto-update
+// scheduling at browser startup time.

[Ken Russell (switch to Gerrit), 2011/10/24 21:04:41]

Could you describe the side-effects of this? In particular, does it allow or
disallow the use of all GPU features?

If this flag is a superset of --ignore-gpu-blacklist, would it make sense to
just add the new behaviors under the existing flag? Interactions between the two
flags could be confusing.

[Zhenyao Mo, 2011/10/24 21:42:19]

Will do.
Good point.  This is kinda tricky.  So here is what I think of:

--ignore-gpu-blacklist is more for the end users.  So for users who opt in this
flag, they could still see the about:gpu content.

--skip-gpu-data-loading will show empty content on about:gpu page, and it is
only for our tests.

Since --ignore-gpu-blacklist is already kinda well-known, I don't think we
should remove it.  So we could either

1) use two separate switches with overlapping effects

or

2) modify the --ignore-gpu-blacklist to do what --skip-gpu-data-loading does in
this CL (only that the name and the behavior will not exactly match).

What do you think?

+const char kSkipGpuDataLoading[]            = "skip-gpu-data-loading";
+
 // Use SQLite as back-end for Indexed Database API.
 // Used for debugging differences between the LevelDB and SQLite back-end.
 const char kSQLiteIndexedDatabase[]         = "indexeddb-use-sqlite";
 
 // Runs the security test for the renderer sandbox.
 const char kTestSandbox[]                   = "test-sandbox";
 
 // A string used to override the default user agent with a custom one.
 const char kUserAgent[]                     = "user-agent";
 
@@ skipping 44 matching lines @@
 // instead of NSS for SSL.
 const char kUseSystemSSL[]                  = "use-system-ssl";
 #endif
 
 #if !defined(OFFICIAL_BUILD)
 // Causes the renderer process to throw an assertion on launch.
 const char kRendererCheckFalseTest[]        = "renderer-check-false-test";
 #endif
 
 }  // namespace switches