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

content/public/common/content_switches.cc

Index: content/public/common/content_switches.cc
===================================================================
--- content/public/common/content_switches.cc	(revision 106917)
+++ content/public/common/content_switches.cc	(working copy)
@@ -442,6 +442,10 @@
 // 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";