Created multi-process-friendly PowerMonitor interface.

chrome/nacl/nacl_main.cc

Index: chrome/nacl/nacl_main.cc
diff --git a/chrome/nacl/nacl_main.cc b/chrome/nacl/nacl_main.cc
index 24f96f2c9fea4688bad5e790368cc676f9e1767d..57d8b90b5963775a1998a9b471b6d85a095bb741 100644
--- a/chrome/nacl/nacl_main.cc
+++ b/chrome/nacl/nacl_main.cc
@@ -6,8 +6,6 @@
 
 #include "base/command_line.h"
 #include "base/message_loop/message_loop.h"
-#include "base/power_monitor/power_monitor.h"
-#include "base/timer/hi_res_timer_manager.h"
 #include "chrome/common/chrome_result_codes.h"
 #include "chrome/common/chrome_switches.h"
 #include "chrome/common/logging_chrome.h"
@@ -24,9 +22,6 @@ int NaClMain(const content::MainFunctionParams& parameters) {
   base::MessageLoopForIO main_message_loop;
   base::PlatformThread::SetName("CrNaClMain");
 
-  base::PowerMonitor power_monitor;
-  base::HighResolutionTimerManager hi_res_timer_manager;
-

[jvoung (off chromium), 2013/07/31 21:24:39]

Note that nacl_main got moved to components, I think.

I'm not familiar with this code, but bbudge did mention that at some point the
NaCl + Pepper timers on Windows would not give > 16ms timer resolution.  Would
that regress w/ this?

 #if defined(OS_WIN) || defined(OS_MACOSX) || defined(OS_LINUX)
   NaClMainPlatformDelegate platform(parameters);