Improving the reliability of commodity operating systems

By Michael M. Swift, Brian N. Bershad, Henry M. Levy. TOCS, 2005

584 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Computer Networks and Communications, Hardware and Architecture

View Paper: https://www.semanticscholar.org/paper/d826316e923e440d64147d37baa0ba866ac3705d

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

1. Gogul Balakrishnan
2. Thomas W. Reps
3. Sriram K. Rajamani
4. Thomas Ball
5. Byron Cook
6. Vladimir Levin
7. Virgil D. Gligor
8. Bohus Ondrusek

In Computer Networks and Communications

1. Thomas W. Reps
2. Gogul Balakrishnan
3. Virgil D. Gligor
4. Armando Fox
5. Thomas Ball
6. James Newsome
7. Sriram K. Rajamani
8. Christopher J. Rossbach

In Hardware and Architecture

1. Thomas W. Reps
2. Gogul Balakrishnan
3. Sriram K. Rajamani
4. Thomas Ball
5. Bohus Ondrusek
6. James Newsome
7. Byron Cook
8. Christopher J. Rossbach

Citations in the corpus

• Thorough static analysis of device drivers (2006, background): “…driver’s StartIo function, and then • the driver’s plug-and-play dispatch routine with an IRP MN REMOVE DEVICE I/O request packet (to simulate the device being removed from the computer) , and finally • the driver’s Unload routine, which the operating sys-tem would call after a device remove event.”
• Building Verifiable Trusted Path on Commodity x86 Computers (2012, background): “First, previous research on device driver implementation in user space [12, 40] and device driver isolation [18, 26, 58] shows how to extract the drivers from the OS kernel in a manner that reduces reliance on the OS for I/O services.”
• Microreboot - A Technique for Cheap Recovery (2004, background): “For example, Nooks [41] isolates drivers within lightweight protection domains inside the operating sys-tem kernel; when a driver fails, it can be restarted without affecting the rest of the kernel.”
• WYSINWYX: What you see is not what you eXecute (2010, methodology): “Several approaches to improve the reliability of device drivers have been previously proposed [Ball et al. 2006; Ball and Rajamani 2001; Chou et al. 2001; Swift et al. 2005].”
• Safe Hardware Access with the Xen Virtual Machine Monitor (2007, background): “While general approaches to partitioning and protecting systems for reliability have been explored over the past thirty years, they often depend on speci(cid:2)c hardware support [3], or are unconcerned with enterprise-class performance and dependability [4, 5].”
• Enhancing Server Availability and Security Through Failure-Oblivious Computing (2004, background): “Helper agents are often useful to facilitate the clean termination and reintegration of the restarted component back into the running system (this approach generalizes to support arbitrary recovery actions) [53].”
• Recovering device drivers (2004, methodology): “3For details on the fault injector see [33].”
• AvA: Accelerated Virtualization of Accelerators (2020, methodology): “Nooks [91] uses kernel-level interposition mechanisms that are similar in spirit to AvA.”
• Terra: a virtual machine-based platform for trusted computing (2003, background): “5.1 Prototype Implementation We built a prototype of the trusted virtual machine monitor us­ing VMware GSX Server 2.0.1 with Debian GNU/Linux as the host operating system.”
• Unmodified Device Driver Reuse and Improved System Dependability via Virtual Machines (2004, background): “The recent Nooks project [33] shares our goal of retrofitting dependability enhancements in commodity systems.”