Revert of Bootstrap Mojo IPC independent of Chrome IPC (patchset #18 id:340001 of https://codereview.chromium.org/1685183004/ )
Reason for revert:
Breaking NaCl in a way that somehow was not caught in the CQ... :{
Will reland once that's sorted out.
Original issue's description:
> Bootstrap Mojo IPC independent of Chrome IPC
>
> This initializes Mojo IPC very early in child process
> startup so we can start using cross-process pipes in
> content without a dependency on Chrome IPC.
>
> On all supported platforms, a new OS pipe handle is
> passed through ChildProcessLauncher and hooked up to
> the EDK on ChildThreadImpl startup to establish a
> Mojo IPC channel to the parent.
>
> A command-line argument is also to used to share a
> unique pipe token with the child, and this token is
> exchanged over the Mojo IPC channel to bootstrap a
> primordial message pipe.
>
> While this CL establishes these facilities in a way
> that can be used for all child processes, only
> render processes are brought up in this way for now.
>
> BUG=583557
> TEST=Chrome still runs in mash with Mus-in-renderer support.
>
> Committed: https://crrev.com/eb199fbaecd8e5d294010dfbe8897b7d83aeab07
> Cr-Commit-Position: refs/heads/master@{#378272}
TBR=ben@chromium.org,jam@chromium.org,jschuh@chromium.org,pennymac@chromium.org,tsepez@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=583557
Review URL: https://codereview.chromium.org/1748973003
Cr-Commit-Position: refs/heads/master@{#378373}
18 files changed
