chrome power profiler chrome side changes

content/browser/browser_thread_impl.cc

Index: content/browser/browser_thread_impl.cc
diff --git a/content/browser/browser_thread_impl.cc b/content/browser/browser_thread_impl.cc
index 099ec3b72a4d4c01ec10ddde08202bb9524185d9..ee47cd29ee3f6e1e3eff73661ee1a57c01b4378c 100644
--- a/content/browser/browser_thread_impl.cc
+++ b/content/browser/browser_thread_impl.cc
@@ -29,6 +29,7 @@ static const char* g_browser_thread_names[BrowserThread::ID_COUNT] = {
   "Chrome_ProcessLauncherThread",  // PROCESS_LAUNCHER
   "Chrome_CacheThread",  // CACHE
   "Chrome_IOThread",  // IO
+  "Chrome_PowerProfilerThread", // POWER_PROFILER

[pfeldman, 2014/01/09 11:38:58]

Why do you want a named thread for power profiler? Could we get away with an ad
hock one?

[qsr, 2014/01/17 11:50:14]

 You seem to jave defined the thread for the power service. Instead you should
do the following:

1) Have the public API of the power service be asynchronous
2) Inside the power service, use a sequenced worker pool to delegate all of you
work, sending back the result asynchronously. You can use
PostTaskAndReplyWithResult to handle all of this.

 };
 
 struct BrowserThreadGlobals {