Refactored Non-SFI and SFI NaCl into separate directories.

mojo/nacl/nonsfi/README.md

Index: mojo/nacl/nonsfi/README.md
diff --git a/mojo/nacl/nonsfi/README.md b/mojo/nacl/nonsfi/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..1d6e517063bda584d3aaa62f4e729ffb63bc880e
--- /dev/null
+++ b/mojo/nacl/nonsfi/README.md
@@ -0,0 +1,63 @@
+About
+=====
+
+This directory contains the necessary components to run Non-SFI NaCl
+nexes (native executables) from within Mojo.
+
+Using
+=====
+
+The Non-SFI NaCl and accompanying tests should be built by default for Linux.
+The boolean indicating if they are built is "mojo_use_nacl_nonsfi", defined
+inside the BUILD files.
+
+Build mojo (all following commands assume you are in the root of the mojo
+repository):
+
+```
+$  ./mojo/tools/mojob.py gn
+$  ./mojo/tools/mojob.py build
+```
+
+Doing this build step will automatically create a pexe of unit tests, at
+`./out/Debug/newlib_pnacl/monacl_test.pexe`.  To translate a pexe into a
+non-SFI nexe:
+
+```
+$ ./native_client/toolchain/linux_x86/pnacl_newlib/bin/pnacl-translate

[Mark Seaborn, 2015/10/12 17:18:50]

How about adding a "\" to the end, since this is split across lines?

[Sean Klein, 2015/10/12 19:10:44]

Done.

+./out/Debug/newlib_pnacl/FOOBAR.pexe -o FOOBAR.nexe -arch x86-32-nonsfi
+```
+
+Now, you should have the fully translated nexe (called
+"FOOBAR.nexe").  You can run the nexe through the monacl shell
+(a minimal, "nexe-only" shell, which loads the nexe ELF file -- see
+ monacl_shell_nonsfi.cc):
+
+```
+$  ./out/Debug/clang_x86/monacl_shell_nonsfi FOOBAR.nexe

[Mark Seaborn, 2015/10/12 17:18:50]

Nit: remove one space after "$"

[Sean Klein, 2015/10/12 19:10:44]

Done.

+```
+
+This monacl_shell_nonsfi is the easiest way to run nexes in mojo -- however, it

[Mark Seaborn, 2015/10/12 17:18:50]

"mojo" -> "Mojo"?

[Sean Klein, 2015/10/12 19:10:44]

Done.

+is not the only way. Usually, applications are launched through the
+"mojo_shell", but some additional information is required to know how to handle
+this content (i.e., how does the mojo_shell know it is dealing with a nonsfi
+nexe?).
+
+The BUILD.gn files in mojo automatically make this pexe, translate it to a
+nexe, and prepend a line ("#!mojo mojo:nacl_content_handler_nonsfi") to the
+front of the file, at which point it is also runnable through the mojo_shell.
+These files, which start with this "#!" line, are ".mojo" files. The nexes can
+be run like this:
+
+```
+$  ./out/Debug/mojo_shell --enable-multiprocess out/Debug/FOOBAR.mojo
+```
+
+TODO
+=============

[Mark Seaborn, 2015/10/12 17:18:50]

Less "="s, to match text?

[Sean Klein, 2015/10/12 19:10:44]

Done.

+
+* Enable content handling of Non-SFI pexes, which should be translated and run
+as nexes.
+  * Use subzero (a NaCl project to improve translation speed) for pexe
+  translation.
+  * Enable caching of translated pexes.