Reland: Bootstrap Mojo IPC independent of Chrome IPC

Reland: Bootstrap Mojo IPC independent of Chrome IPC

The original CL:
https://crrev.com/eb199fbaecd8e5d294010dfbe8897b7d83aeab07

broke NaCL integration tests on some bots. After some
extensive investigation this is somehow tied to an
obscure dependency on the value of kIPCDescriptorMax.
Moving kMojoIPCChannel to content_descriptors.h allows
us to avoid changing that value and thus avoid the
mysterious breakage. :|

Original CL description follows:

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.
TBR=ben@chromium.org,jschuh@chromium.org

Committed: https://crrev.com/e8b8da4b8f513b7ab03bb2e2eb9156bc828267a5
Cr-Commit-Position: refs/heads/master@{#378704}

[Ken Rockot(use gerrit already), 2016-03-01 16:53:42]

The CQ bit was checked by rockot@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-03-01 16:53:58]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1747053003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1747053003/1

[commit-bot: I haz the power, 2016-03-01 18:12:34]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-01 18:12:34]

Dry run: This issue passed the CQ dry run.

[Ken Rockot(use gerrit already), 2016-03-02 04:51:10]

Description was changed from

==========
Reland: 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}

patch from issue 1685183004 at patchset 340001
(http://crrev.com/1685183004#ps340001)
==========

to

==========
Reland: Bootstrap Mojo IPC independent of Chrome IPC

The original CL:
https://crrev.com/eb199fbaecd8e5d294010dfbe8897b7d83aeab07

broke NaCL integration tests on some bots. After some
extensive investigation this for some reason is tied to
some extremely obscure dependency on the value of the
kIPCDescriptorMax enum. Moving kMojoIPCChannel to
content_descriptors.h allows us to preserve the value
of kIPCDescriptorMax and avoid the mysterious breakage.
:|

Original CL description follows:

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.
TBR=ben@chromium.org,jschuh@chromium.org
==========

[Ken Rockot(use gerrit already), 2016-03-02 04:52:12]

Description was changed from

==========
Reland: Bootstrap Mojo IPC independent of Chrome IPC

The original CL:
https://crrev.com/eb199fbaecd8e5d294010dfbe8897b7d83aeab07

broke NaCL integration tests on some bots. After some
extensive investigation this for some reason is tied to
some extremely obscure dependency on the value of the
kIPCDescriptorMax enum. Moving kMojoIPCChannel to
content_descriptors.h allows us to preserve the value
of kIPCDescriptorMax and avoid the mysterious breakage.
:|

Original CL description follows:

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.
TBR=ben@chromium.org,jschuh@chromium.org
==========

to

==========
Reland: Bootstrap Mojo IPC independent of Chrome IPC

The original CL:
https://crrev.com/eb199fbaecd8e5d294010dfbe8897b7d83aeab07

broke NaCL integration tests on some bots. After some
extensive investigation this is somehow tied to an
obscure dependency on the value of kIPCDescriptorMax.
Moving kMojoIPCChannel to content_descriptors.h allows
us to avoid changing that value and thus avoid the
mysterious breakage. :|

Original CL description follows:

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.
TBR=ben@chromium.org,jschuh@chromium.org
==========

[Ken Rockot(use gerrit already), 2016-03-02 04:52:29]

The CQ bit was checked by rockot@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-03-02 04:52:36]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1747053003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1747053003/20001

[commit-bot: I haz the power, 2016-03-02 06:07:49]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-02 06:07:50]

Dry run: This issue passed the CQ dry run.

[Ken Rockot(use gerrit already), 2016-03-02 06:13:44]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2016-03-02 06:13:59]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1747053003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1747053003/20001

[commit-bot: I haz the power, 2016-03-02 06:20:34]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-03-02 06:21:49]

Description was changed from

==========
Reland: Bootstrap Mojo IPC independent of Chrome IPC

The original CL:
https://crrev.com/eb199fbaecd8e5d294010dfbe8897b7d83aeab07

broke NaCL integration tests on some bots. After some
extensive investigation this is somehow tied to an
obscure dependency on the value of kIPCDescriptorMax.
Moving kMojoIPCChannel to content_descriptors.h allows
us to avoid changing that value and thus avoid the
mysterious breakage. :|

Original CL description follows:

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.
TBR=ben@chromium.org,jschuh@chromium.org
==========

to

==========
Reland: Bootstrap Mojo IPC independent of Chrome IPC

The original CL:
https://crrev.com/eb199fbaecd8e5d294010dfbe8897b7d83aeab07

broke NaCL integration tests on some bots. After some
extensive investigation this is somehow tied to an
obscure dependency on the value of kIPCDescriptorMax.
Moving kMojoIPCChannel to content_descriptors.h allows
us to avoid changing that value and thus avoid the
mysterious breakage. :|

Original CL description follows:

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.
TBR=ben@chromium.org,jschuh@chromium.org

Committed: https://crrev.com/e8b8da4b8f513b7ab03bb2e2eb9156bc828267a5
Cr-Commit-Position: refs/heads/master@{#378704}
==========

[commit-bot: I haz the power, 2016-03-02 06:21:50]

Patchset 2 (id:??) landed as
https://crrev.com/e8b8da4b8f513b7ab03bb2e2eb9156bc828267a5
Cr-Commit-Position: refs/heads/master@{#378704}