Move gpu blacklist to content side.

Move gpu blacklist to content side.

When it's on the content side, it can be part of the GpuDataManager, so we don't need to make it a Singleton.

Also, this CL did some cleanup related to this moving.

The main reason for this refactoring is because blacklist is tightly coupled with GpuDataManager.  Putting them on the this side makes it much easier to test the code, and the design is much better.

BUG=
TEST=bots
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=155218

[Zhenyao Mo, 2012-09-05 23:22:13]

Please review.

[jbates, 2012-09-06 00:50:41]

LGTM with nits

https://chromiumcodereview.appspot.com/10908110/diff/1033/content/browser/gpu...
File content/browser/gpu/gpu_data_manager_impl.cc (left):

https://chromiumcodereview.appspot.com/10908110/diff/1033/content/browser/gpu...
content/browser/gpu/gpu_data_manager_impl.cc:64: switches::kSkipGpuDataLoading))
Just making sure you meant to remove the kSkipGpuDataLoading feature?

https://chromiumcodereview.appspot.com/10908110/diff/1033/content/browser/gpu...
File content/browser/gpu/gpu_util.h (right):

https://chromiumcodereview.appspot.com/10908110/diff/1033/content/browser/gpu...
content/browser/gpu/gpu_util.h:33: uint32 blacklisted_features);
nit: need some comments about these params

[Zhenyao Mo, 2012-09-06 00:59:45]

https://chromiumcodereview.appspot.com/10908110/diff/1033/content/browser/gpu...
File content/browser/gpu/gpu_data_manager_impl.cc (left):

https://chromiumcodereview.appspot.com/10908110/diff/1033/content/browser/gpu...
content/browser/gpu/gpu_data_manager_impl.cc:64: switches::kSkipGpuDataLoading))
On 2012/09/06 00:50:41, jbates wrote:
> Just making sure you meant to remove the kSkipGpuDataLoading feature?

Yes, it's taken care of from the caller side.

[sadrul, 2012-09-06 19:48:13]

It looks like this broke chromeos bots:
http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%2...

http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%2...