Move chromeos::device_event_log into components.

chrome/browser/chrome_browser_main.cc

Index: chrome/browser/chrome_browser_main.cc
diff --git a/chrome/browser/chrome_browser_main.cc b/chrome/browser/chrome_browser_main.cc
index 69ccdf4f11f3061a33268fea3f7ae4dc90c064d3..7dc7691619c80db5464a607543832e13487aefaf 100644
--- a/chrome/browser/chrome_browser_main.cc
+++ b/chrome/browser/chrome_browser_main.cc
@@ -105,6 +105,7 @@
 #include "chrome/grit/generated_resources.h"
 #include "chrome/installer/util/google_update_settings.h"
 #include "components/component_updater/component_updater_service.h"
+#include "components/device_event_log/device_event_log.h"
 #include "components/google/core/browser/google_util.h"
 #include "components/language_usage_metrics/language_usage_metrics.h"
 #include "components/metrics/metrics_service.h"
@@ -760,6 +761,9 @@ void ChromeBrowserMainParts::ToolkitInitialized() {
 
 void ChromeBrowserMainParts::PreMainMessageLoopStart() {
   TRACE_EVENT0("startup", "ChromeBrowserMainParts::PreMainMessageLoopStart");
+
+  device_event_log::Initialize(0 /* default max entries */);
+
   for (size_t i = 0; i < chrome_extra_parts_.size(); ++i)
     chrome_extra_parts_[i]->PreMainMessageLoopStart();
 }
@@ -1691,6 +1695,8 @@ void ChromeBrowserMainParts::PostMainMessageLoopRun() {
 
   browser_process_->metrics_service()->Stop();
 
+  device_event_log::Shutdown();

[stevenjb, 2015/02/17 21:29:51]

Lets do this in PostDestryThreads which matches where we currently do it in
Chrome OS and shouldn't cause any problems.

+
   restart_last_session_ = browser_shutdown::ShutdownPreThreadsStop();
   browser_process_->StartTearDown();
 #endif