http://papersincomputerscience.org/2009/12/19/efficient-software-based-fault-isolation/ Discussion of computer science publications Wed, 25 Jan 2012 11:32:47 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://papersincomputerscience.org/2009/12/19/efficient-software-based-fault-isolation/#comment-70 Efficient Software-Based Fault Isolation « Papers in Computer Science | PC News Thu, 07 Jan 2010 19:57:05 +0000 http://papersincomputerscience.org/?p=174#comment-70 [...] here: Efficient Software-Based Fault Isolation « Papers in Computer Science 1993-paper, fault-isolation, frequently-communicating, improve-end-to-end, lucco, wahbe یک [...] [...] here: Efficient Software-Based Fault Isolation « Papers in Computer Science 1993-paper, fault-isolation, frequently-communicating, improve-end-to-end, lucco, wahbe یک [...]

]]> http://papersincomputerscience.org/2009/12/19/efficient-software-based-fault-isolation/#comment-69 davidhi Wed, 23 Dec 2009 06:34:44 +0000 http://papersincomputerscience.org/?p=174#comment-69 One artifact that builds on these foundational techniques is Google's <a href="http://code.google.com/p/nativeclient/" rel="nofollow">Native Client</a> (NaCl) browser plugin. Their <a href="http://nativeclient.googlecode.com/svn/data/docs_tarball/nacl/googleclient/native_client/documentation/nacl_paper.pdf" rel="nofollow">paper</a> on Native Client and its sandboxing techniques won best paper at IEEE Security & Privacy this year. Funny you should mention that you are skeptical of Vx32's use of x86 segmentation because NaCl uses it too. Back when AMD was defining the 64-bit x86 architecture, they got rid of segmentation as "legacy baggage" but ended up adding it back in because VMware used it heavily (before they offered hardware virtualization instructions). Michael Steil has an interesting <a href="http://www.pagetable.com/?p=25" rel="nofollow">writeup</a> on that particular situation. One artifact that builds on these foundational techniques is Google’s Native Client (NaCl) browser plugin. Their paper on Native Client and its sandboxing techniques won best paper at IEEE Security & Privacy this year. Funny you should mention that you are skeptical of Vx32′s use of x86 segmentation because NaCl uses it too. Back when AMD was defining the 64-bit x86 architecture, they got rid of segmentation as “legacy baggage” but ended up adding it back in because VMware used it heavily (before they offered hardware virtualization instructions). Michael Steil has an interesting writeup on that particular situation.

]]>