Show Compositor information in chrome://gpu

content/browser/gpu/compositor_util.cc

Index: content/browser/gpu/compositor_util.cc
diff --git a/content/browser/gpu/compositor_util.cc b/content/browser/gpu/compositor_util.cc
index 64b5e8737af2ac0be70a35b0123bde38a2ceb8a4..1bec632390922df490ff25a7144077bd98622abe 100644
--- a/content/browser/gpu/compositor_util.cc
+++ b/content/browser/gpu/compositor_util.cc
@@ -34,6 +34,7 @@ const char* kGpuCompositingFeatureName = "gpu_compositing";
 const char* kWebGLFeatureName = "webgl";
 const char* kRasterizationFeatureName = "rasterization";
 const char* kMultipleRasterThreadsFeatureName = "multiple_raster_threads";
+const char* kNativeGpuMemoryBuffersFeatureName = "native_gpu_memory_buffers";
 
 const int kMinRasterThreads = 1;
 const int kMaxRasterThreads = 4;
@@ -154,6 +155,13 @@ const GpuFeatureInfo GetGpuFeatureInfo(size_t index, bool* eof) {
           "Raster is using a single thread.",
           false
       },
+      {
+          kNativeGpuMemoryBuffersFeatureName,
+          false,
+          !BrowserGpuMemoryBufferManager::IsNativeGpuMemoryBuffersEnabled(),
+          "Native GpuMemoryBuffer is not supported.",

[reveman, 2016/01/29 15:43:50]

This is not necessarily true. As the default is still disabled, should we invert
this? "Native GpuMemoryBuffer are enabled"?

[dshwang, 2016/01/29 16:46:14]

it's disabled_description.
"Problems Detected" in chrome://gpu shows as follows:
Native GpuMemoryBuffer is not supported.
Disabled Features: native_gpu_memory_buffers

Chrome Linux shows the disabled_description. I think it's correct description,
because it's why we don't turn it on in linux and windows.

let me copy&paste another example:
Accelerated rasterization has been disabled, either via about:flags or command
line.
Disabled Features: rasterization

+          true
+      },
   };
   DCHECK(index < arraysize(kGpuFeatureInfo));
   *eof = (index == arraysize(kGpuFeatureInfo) - 1);