Remove IOThread::message_loop().

Instead introduce BrowserThread::UnsafeGetMessageLoop which is used in
a couple of places.  This will be removed in a follow-up change.  I
could have used UnsafeGetBrowserThread(id)->message_loop() but this is
even easier to search for.

Also, remove a couple of BrowserProcess accessors that aren't used by anybody, and that were using UnsafeGetBrowserThread.

TBR=battre@chromium.org
BUG=98716


Review URL: http://codereview.chromium.org/8775014

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112697 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 7 insertions, 9 deletions

diff --git a/chrome/browser/process_singleton_linux.cc b/chrome/browser/process_singleton_linux.cc
index cbf6492f..34feef1 100644
--- a/chrome/browser/process_singleton_linux.cc
+++ b/chrome/browser/process_singleton_linux.cc
@@ -995,15 +995,13 @@ bool ProcessSingleton::Create() {
   if (listen(sock, 5) < 0)
     NOTREACHED() << "listen failed: " << safe_strerror(errno);
 
-  // Normally we would use BrowserThread, but the IO thread hasn't started yet.
-  // Using g_browser_process, we start the thread so we can listen on the
-  // socket.
-  MessageLoop* ml = g_browser_process->io_thread()->message_loop();
-  DCHECK(ml);
-  ml->PostTask(FROM_HERE, base::Bind(
-    &ProcessSingleton::LinuxWatcher::StartListening,
-    watcher_.get(),
-    sock));
+  DCHECK(BrowserThread::IsMessageLoopValid(BrowserThread::IO));
+  BrowserThread::PostTask(
+      BrowserThread::IO,
+      FROM_HERE,
+      base::Bind(&ProcessSingleton::LinuxWatcher::StartListening,
+                 watcher_.get(),
+                 sock));
 
   return true;
 }