1. OmniVM Efficient and Language- Independent Mobile Programs Ali-Reza Adl-Tabatabai, Geoff Langdale, Steven Lucco and Robert Wahbe from Carnegie Mellon University and Colusa Software presented by Suming Chen April 16, 1998

2. Motivations n Two ways to ensure safe execution of mobile code: u Language semantics u Abstract machine interpretation n Goals u Portable F run on any machine F safe execution of any source language u Efficient F fast translation u Easy to generate code

3. What is OmniVM? n A safe, efficient, and language-independent system for executing mobile program modules n RISC-based design u instruction set, register file organization, data format, exception model, and segmented virtual memory model

4. System Overview C compiler JAVA compiler ML compiler Fortran compiler Source program C source JAVA source ML source Fortran source Compiler Mobile Object Mobile Code MIPS translator SPARC translator PowerPC translator x86 translator Host translator Loaded native executable MIPS object SPARC object PowerPC object x86 object...

5. Safety n Use software fault isolation (SFI) to enforce safety n Host-imposed permission on address spaces n Inline checks during load time and translation time n In case of violation, delivers access violation exception

6. Performance n Measured on u 90 MHz Intel Pentium based “Precision Pentium” running Windows NT 3.5 u PowerPC 601 based IBM RS/6000 running AIX version 3 u Mips R4400 based SGI Indigo-2 machine running Irix 5.2 u Sparc based SPARC10 running Solaris 2.4 n Use four C programs from SPEC92 suite u li, compress, alvinn, and eqntott

7. Performance con’t... Execution time of mobile code relative to native code generated by cc

8. Performance con’t... Execution time of mobile code relative to native code generated by gcc

9. Performance con’t... Execution time of mobile code without translator optimization, relative to native code generated by cc.

10. Conclusion n Including the overhead for enforcing safety, OmniVM executed benchmark programs within 21% as fast as the optimized, unsafe native code n Fastest system for mobile code n First to implement safe, mobile code efficiently and language-independently

11. Final Remarks n Need to retarget compilers n Requires machine-dependent translator residing on the host machine and these translators need to have prior information on which segments in the memory are safe for the mobile code n Current OmniVM does not support read protection