B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In USENIX, editor, 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), October 28--31, 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....up sufficient low pages for remapping I O pages that are currently hot. We are currently exploring various techniques, ranging from simple random replacement to adaptive approaches based on cost benefit tradeoffs. 8 Related Work Virtual machines have been used in numerous research projects [3, 7, 8, 9] and commercial products [20, 23] over the past several decades. ESX Server was inspired by recent work on Disco [3] and Cellular Disco [9] which virtualized shared memory multiprocessor servers to run multiple instances of IRIX. ESX Server uses many of the same virtualization techniques as ....

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullman, Godmar Back, and Stephen Clawson. "Microkernels Meet Recursive Virtual Machines," Proc. Symposium on Operating System Design and Implementation, October 1996.

....from a centralized implementation (with a single shared rep) to a distributed one (with a rep per processor) 1.2 Dynamic Customization in K42 Building blocks provide tremendous flexibility in allowing K42 to be customized for an application. As other work in customizable systems demonstrates [3, 4, 6, 8, 9, 26], this flexibility can translate into significant performance gains. Often times though, when a resource is first accessed, it is not clear, especially from the operating system s perspective, what its request pattern will be. Also, an application s use of operating system resources may change ....

....summarizes our mechanism and results, and describes possible future work. Related Work A number of research operating system projects have explored customizability. Recent research in extensible and customizable operating systems includes SPIN [3, 22] VINO [26, 27] Exokernel [8] Fluke [9], L4 [18] Cache Kernel [6] Choices [4] Nemesis [17] Scout [20] and K42 [2] Many of the above operating systems achieve customizability by extensibility. The Exokernel, Fluke, L4, and Cache Kernel allow for customizability by having the kernel redirect hardware events to external address ....

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proc. 2nd Symp. on Operating Systems Design and Implementation, pages 137--152, 1996.

....code to a virtual desktop inside Windows 2000. However, because it is implemented inside a conventional operating system, WindowBox s security is limited by high level abstractions and global namespaces. By virtualizing at a layer below operating system abstractions, VMMs are more secure. Fluke [23] proposes a recursive VM model, in which a parent can re implement OS functionality on behalf of its child processes. In Denali, we virtualize at a layer below OS abstractions, whereas Fluke s virtual architecture includes high level IPC calls. By virtualizing at the level of hardware, we avoid ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the Second Symposium on Operating Systems Design and Implementation, October 1996.

....our goal of isolating performance between competing applications. Nemesis adopts a similar approach, pushing most kernel functionality to user level. Nemesis was not designed to sandbox untrusted code; Nemesis applications share a global le system and a single virtual address space. The Fluke OS [13] proposes a recursive virtual machine model, in which a parent can re implement OS functionality on behalf of its children. Like Denali, Fluke exposes private namespaces through its state encapsulation property. The primary motivation for this is to support checkpointing and migration, though ....

B. Ford et al. Microkernels meet recursive virtual machines. In Proceedings of the Second Symposium October 1996.

....with each other is left to the authors of the user level system services and the developers of subsequent customizations. The Utah Flux project has constructed a software architecture that supports replacement of operating system components, particularly nesting of operating system components [19, 20] using the recursive virtual machine concept. Each virtual machine level can be customized for specific needs, and is protected from other virtual machines at the same level. The layers of indirection implicit in this structure come at some cost. However, specialization may be able to minimize ....

Ford, B., M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels Meet Recursive Virtual Machines. in Symposium on Operating Systems Design and Implementation (OSDI). 1996.

....functionality is provided by components, which implement units of functionaly. Environments serve as the new unifying abstraction: They are containers for stored tuples, components, and other environments, providing a combination of the roles served by file system directories and nested processes [5, 12, 24] in more traditional operating systems. Environments make it possible to group data and functionality when necessary. At the same time, they allow for data and functionality to evolve separately and for applications to store and exchange just data, thus avoiding the two problems associated with ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the 2nd USENIX Symposium on Operating Systems Design and Implementation, pages 137--151, Seattle, Washington, Oct. 1996.

....and by designing adaptive applications which can employ different algorithms depending on which resources are scarce. However, they admit that global performance has not been extensively studied [Kaashoek97] Ford et al. present an alternative approach based on recursive virtual machines [Ford96a] They use the term virtual machine more generally than in this dissertation, using it to denote any execution environment such as that provided by an operating system to the applications running over it and interacting with it through a virtual machine interface (vmi) A recursive virtual ....

....as that provided by an operating system to the applications running over it and interacting with it through a virtual machine interface (vmi) A recursive virtual machine is therefore one vm running over another, usually customizing the vmi in some way. This architecture was implemented in Fluke [Ford96a] It enables a modular os design in which functionality may be implemented at different levels within a series of nested vms or nesters. Unneeded services may be removed and existing services re implemented or customized. Nesters form a hierarchy and so different applications or groups of ....

Bryan Ford, Mike Hibler, Jay Lapreau, Patrick Tullmann, Godmar Back, and Stephen Clawson. Microkernels meet recursive virtual machines. In Proceedings of the 2nd Symposium on Operating Systems Design and Implementation (OSDI '96). The USENIX Association, October 1996. Also appeared as University of Utah, Department of Computer Science Technical Report UUCS-96-004. (p 36)

....IPC mechanisms are designed in a way such that whenever there is a thread interaction, the service dependency information is implicitly made available to the operating system. This has been typically adopted by component based operating systems such as Mach [8, 27] Exokernel [20] Fluke [26, 25], Spring kernel [35] Pebble [29] etc. In a general purpose operating system running on most PCs and enterprise servers, it is not always feasible to modify existing applications to either explicitly notify the operating system or to start using a specially designed IPC mechanism. Since the ....

....designed in a way such that whenever threads interact with each other using these mechanisms, the service dependency information is implicitly made available to the operating system. This has been typically adopted by component based operating systems such as Mach [8, 27] Exokernel [20] Fluke [26, 25], Spring kernel [35] Pebble [29] etc. Most of these operating systems are still in the prototype stage, they represent the current state of art in operating system design and implementation, and possess great potential. However, these systems still run much fewer applications than commercial ....

[Article contains additional citation context not shown here]

B. Ford, M. Hilber, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels Meet Recursive Virtual Machines. In Proceedings of 2nd Symposium on Operating Systems Design and Implementation, pages 137--151, 1996.

....are also an important mechanism for dynamic composition: an environment controls all nested environments and can interpose on their interactions with the kernel and the outside world. Environments thus represent a combination of the roles served by file system directories and nested processes [6, 18, 43] in more traditional operating systems. Figure 2 shows an example environment hierarchy. Access to both local and remote resources is controlled by leases [22] Leases limit the time applications can access resources, such as an environment s tuple storage or a communication channel, and force ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the 2nd USENIX Symposium on Operating Systems Design and Implementation, pages 137--151, Oct. 1996.

....requirements for establishing an exchange. 3.3.3.11 Fluke The Flux Research Group (FRG) at the University of Utah are extremely active in the field of general operating system research. Their projects include; Java operating systems (see section 3.3.3. 9) the OSKit [Ford,97a] Ford,97b] Fluke [Ford,96] and Flask. The OSKit is an effort to remove the drudgery from developing native operating systems on behalf of the operating system research community by collating and documenting source code from various free software projects (plus Utah s own contributions, particularly in bootstrap and ....

Ford, B., Hibler, M., Lepreau, J., Tullmann, P., Back, G., Clawson, S., "Microkernels Meet Recursive Virtual Machines". Proceedings of the Second USENIX Symposium on Operating System Design and Implementation (OSDI'96), pp 137-151, Seattle WA, U.S.A., October 1996

....group stored data, application components, and hierarchically, other environments. They simplify management of users, their applications, and their data. They can be thought of as a combination of file system directories and nested processes in terms of more traditional operating systems [2, 3, 6]. They group related code and data so that they can be migrated together, for example. These abstractions are crucial to the implementation of the services that will be used by developers of ubiquitous computing applications. They provide an ability to compose applications dynamically. We ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the 2nd USENIX Symposium on Operating Systems Design and Implementation, pages 137--151, Oct. 1996.

....crucial. 7.1 Requirements The J SEAL2 kernel manages a tree hierarchy of nested protection domains. The resource control facilities shall reflect the hierarchical system structure. Hierarchical process models have been used successfully by operating system kernels, such as the Fluke microkernel [8]. The Fluke kernel employs a hierarchical scheduling protocol, CPU Inheritance Scheduling [9] in order to enforce scheduling policies. In this model, a parent domain donates a certain percentage of its own CPU resources to a child process. Initially, the root of the hierarchy possesses all CPU ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels Meet Recursive Virtual Machines. In Proceedings of the Second Symposium on Operating Systems Design and Implementation (OSDI'96), October 1996. Available at http://www.cs.utah.edu/flux/papers/fluke-rvm.ps.gz

....records with named elds, while functionality is provided by components. Environments serve as the new unifying abstraction: They are containers for stored tuples, active components, and other environments, providing a combination of the roles served by le system directories and nested processes [5, 11] in more traditional operating systems. Environments make it possible to group data and functionality when necessary. At the same time, they allow for data and functionality to evolve separately and for applications to store and exchange just data, thus avoiding the two problems associated with ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the 2nd USENIX Symposium on Operating Systems Design and Implementation, pages 137-151, Seattle, Washington, Oct. 1996.

....be treated specially in her text editor. While it is not feasible to analyse or modify large third party software packages, it is possible to intercept the communications between a package and the other parts of the system, interposing code at the boundaries of the different software components [20, 11, 7, 13]. It is thus possible to monitor or control the operations that these components are able to invoke, and the data that is exchanged between them. We call a code fragment that encapsulates untrusted components a security wrapper or wrapper for short. Clearly the task of writing wrappers should not ....

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In USENIX, editor, 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), October 28--31, 1996. Seattle, WA, pages 137--151, Berkeley, CA, USA, Oct. 1996. USENIX.

....If some node wants to talk to other nodes, it needs to talk first to KDC [41, 58] In the case of Mach and capability interposition, all kernels on all nodes are 15 part of a trust domain and all kernel ports are trusted. User level task migration breaks this concepts. The work by Ford et al. [24, 25] bridges the gap between OS and agent work. Ford et al. introduce the recursive virtual machines that allow the code to execute in a separate trusted domain. SPIN system addresses security by enabling the secure execution of the code within the kernel. In particular it addresses the kernel ....

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, S. Clawson, "Microkernels Meet Recursive Virtual Machines," Proceedings of the USENIX Second Symposium on Operating Systems Design and Implementation (OSDI'96), Seattle WA, October 1996, pp 137-152.

....messages sent from its children to other seals in its environment, and imposes security constraints on these messages. In contrast, a seal is not able to peek and poke the internals of any of its children seals, or of any other seal. The design has been inspired by the Fluke micro kernel [14] and work on interposition in operating systems [12, 15, 16] We have not addressed interposition of low level resources such as memory and the scheduler as this requires modifications to the virtual machine [3] Two types of agents: In JavaSeal there are two categories of agents. The leaves of ....

....we argue that no real change to the JVM is needed to achieve this level of security, rather a fundamental redesign of the JDK. Protection domains are also an operating system issue and many of the ideas here are influenced by such work. For instance, the hierarchial model is influenced by Fluke [14] and L3 [27] as well as by work on interposition [12, 15, 16] 8 Conclusion This paper has described the JavaSeal platform. This is a secure kernel for mobile environments (envlets) and mobile objects (complets) JavaSeal is a kernel in that it offers minimal service funtionality. Since ....

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In USENIX, editor, 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), October 28--31, 1996. Seattle, WA, pages 137--151, Berkeley, CA, USA, Oct. 1996. USENIX.

....works atop the hardware platform to provide an isolated computing environment [64] Another way is to provide a multisetting environment within a single OS to accommodate multiple independent computing environments for applications. University of Utah has developed nested process architecture [65] based on a micro kernel OS, where multiple settings can be realized by decomposing kernellevel services into user level processes and by accessing those services via nesting of processes. For the purpose of softnode implementation within the Linux kernel, we pursue a similar approach to the ....

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullmann, Godmar Back, Stephen Clawson, "Microkernels Meet Recursive Virtual Machines," In Proceedings of the Second Symposium on Operating Systems Design and Implementation, Seattle, WA, October 1996, USENIX Assoc.

....In addition, we reduce the scope of our effort by ignoring fairness conditions. For convenience, we denote I and #N # v in the component state as init and steps, respectively. Our example is drawn from the research of secure, microkernel based, operating system architectures, such as Fluke [3]. Consider a simple, generic (i.e. non securityrelevant) system consisting of three object managers (ignore the kernel) a file server, a process manager and a memory manager. The system is illustrated in Figure 1. file server memory manager process manager fhandle name data fhandle ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the Symposium on Operating Systems Design and Implementations (OSDI), Oct. 1996.

....or asynchronous IPC. On the other hand, applications can choose not to use protected control transfer and implement IPC another way. For example, through shared memory and priority scheduling, as done on UNIX. 1.1. 4 Unprivileged Extensibility Requires Protected Sharing Some extensible systems [1, 8, 16, 30] allow applications to alter system behaviors by inserting application specific extensions. To ensure safety, these systems often apply restrictions on where and how extensions can be inserted and executed. In comparison, the exokernel approach to extensibility provides more power: an exokernel ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proc. of the Second Symposium on Operating Systems Design and Implementation, October 1996.

....(DSLs) and offers rapid development of robust OSes. We illustrate and assess our approach by concrete examples. 1 Existing OS Approaches An OS (or an OS sub system) conventionally consists of two levels: mechanisms and policies. Mechanisms can take the form of libraries [7] or abstract machines [8]. Policies correspond to algorithms based on mechanisms. Ideally, a policy should be implemented as code gluing mechanisms together. In practice, the separation between these two levels is not systematically achieved. This lack of separation makes it difficult to understand and reason about the ....

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In OSDI'96 [16], pages 137--151.

....that the architecture is sound. The Fluke Assurance program focused primarily upon the changes to the Fluke microkernel and Security Server, but also provided some review of proposed changes in other Fluke object managers. The base Fluke system provides a recursive virtual machine architecture [7] which is intended to support isolation of processes for security and other reasons. The first task on the Fluke Assurance program was to investigate this architecture in order to identify the requirements that this architecture places on the various system components. In doing so, we found that ....

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullmann, Godmar Back, and Stephen Clawson. Microkernels meet recursive virtual machines. In Proceedings of the Symposium on Operating Systems Design and Implementations (OSDI), October 1996.

....tasks should execute [21] The ability to get specific finegrained amounts of resources, under process control, is lacking in most popular operating systems. However, new research systems are beginning to address this problem, including Exokernel [47] L5 [91] SPIN [22] Cache Kernel [31] Fluke[54], and Scout[102] Our approach differs either in the level of abstraction provided, or the granularity of resource control, or both. G.2.3.3 Network Communication Support Agents need to communicate with the client they left behind, with servers they visit, and, of course, with other agents. We ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson, "Microkernels Meet Recursive Virtual Machines," Proceedings of OSDI '96, 1996. 64

....and schedule higher priority tasks as soon as they are ready to run completely independent of task deadlines. An alternative is to use a proportional share scheduler to allocate some some fraction of the CPU to each task, where proportions are often allocated in a hierarchical fashion [13, 6, 7, 2, 12, 4]. 1 Proportional share schedulers are all descended from the fair queuing algorithm originally developed to schedule packets for transmission in a network switch [3] Percent deadlines missed 0 5 10 15 20 25 30 0 2 4 6 8 10 Percent realtime share too small Figure 1: ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proc. of the Second Symposium on Operating Systems Design and Implementation, pages 137--151, Seattle, WA, Oct. 1996. USENIX Assoc.

....operating systems. Extensible operating systems can easily adapt to satisfy the requirements of new emerging applications. The growing importance of extensibility is evidenced by the numerous projects focusing on designing new extensible operating systems [Bershad et al. 1995; Engler et al. 1995; Ford et al. 1996; Seltzer et al. 1994] or implanting extensibility in existing ones [Fitzhardinge 1996; Ghormley et al. 1996] In this article we present a new method for extending existing operating systems entirely at the user level. We achieve most of the benefits of an extensible operating system without ....

....the kernel. Engler et al. 1995] propose to implement the operating system as a set of untrusted application libraries. In their approach the kernel is reduced to a very small exokernel that is only responsible for securely exporting the hardware resources to the library operating system. Fluke [Ford et al. 1996] combines the microkernel approach with recursive virtual machines [Goldberg 1974] This produces a modular and extensible operating system which can be decomposed both horizontally (as in microkernel OS) and vertically through stackable virtual machine monitors. Another approach, taken by VINO ....

FORD, B., HIBLER, M., LEPREAU, J., TULLMAN, P., BACK, G., AND CLAWSON, S. 1996. Microkernels meet recursive virtual machines. In Proceedings of the 2nd Symposium on Operating Systems Design and Implementation (OSDI '96, Seattle, WA, Oct.). ACM Press, New York, NY.

....location, and open, which moves all contents of an environment into the enclosing environment and deletes the emptied environment. Furthermore, tasks can request to be notified when other environments are moved into or out of their environment. Like nested process structures in other systems [4, 10, 31], the hierarchical nesting of environments provides control. In particular, environments use leases [14] and quotas to limit the resources available to enclosed tasks, tuples, and other environments and to facilitate the e#ective reclamation of these resources. To ensure security, they also ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the Second Symposium on Operating Systems Design and Implementation, pages 137--151, Seattle, Washington, Oct. 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullmann, Godmar Back, and Stephen Clawson. Microkernels meet recursive virtual machines. In Proceedings of the Second Symposium on Operating Systems Design and Implementation, pages 137--151, Seattle, WA, October 1996. USENIX Association.

....and resource control. This task also mirrors the responsibility of an operating system kernel. For example, a kernel must bound IPC port queues to ensure that one process does not deny communications service to another process. In systems that employ capabilities, such as Mach [1] or Fluke [36], the kernel must track capabilities to ensure that a process does not acquire communication rights that it should not have. In systems that provide shared memory or memory mapped files, the kernel provides memory that is shared between processes. The memory mappings into the participating ....

....from high overhead. In addition, it makes resource accounting incomplete, because allocations within internal VM code cannot be accounted for. 6.1. 4 Alta The Alta [79, 80] system provides an environment that runs multiple applications in a single JVM that is modeled after the Fluke microkernel [36]. The Fluke microkernel provides a nested process model, in which a parent process controls all aspects of its child process. It does so by interposing on the child s communication, which is done via IPC. As in many microkernels, system services are provided through servers, which complicates ....

Ford, B., Hibler, M., Lepreau, J., Tullmann, P., Back, G., and Clawson, S. Microkernels meet recursive virtual machines. In Proceedings (Seattle, WA, October 1996), USENIX Association, pp. 137--151.

....well functioning distributed system places on the local OS, and particularly emphasized endsystem security in the widespread presence of mobile code. The focus of that paper was on making the case for the importance of the local OS, and outlining an appropriate OS for that environment: the Fluke [6] operating system, an OS based on a recursive virtual machine model, analogous to the Cambridge CAP Computer [24] but implemented by a microkernel instead of special hardware. In this paper we assume that the importance of the local OS to distributed applications is evident. From that base, we ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels Meet Recursive Virtual Machines. In Proc. of the SecondSymp. on Operating Systems Design andImplementation, pages 137--151, Seattle, WA, Oct. 1996. USENIX Assoc.

....or asynchronous stubs (or both) Because there are multiple ways in which one might present a single IDL interface, Flick provides multiple presentation generators for creating different kinds of stubs. As shown in Figure 1, Flick includes presentation generators for CORBA , rpcgen , Fluke [14], and MIG style C language stubs. Moreover, Flick provides the infrastructure for producing altogether new kinds of stubs, either through the creation of new presentation generators or through extensions to Flick s base presentation generator library. The output of a presentation generator is ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the Second Symposium on Operating Systems Design and Implementation, pages 137--151, Seattle, WA, Oct. 1996. USENIX Assoc.

....must be engineered to provide fast, efficient communication. In this paper we compare several Java systems, and the process models that they support: Alta and K0, two projects at the University of Utah, and the J Kernel, a project at Cornell. Alta is structured much like the Fluke microkernel [22], provides a hierarchical process model, and focuses on providing safe, efficient sharing between processes with potentially different type spaces. K0 is structured much like a traditional monolithic kernel and focuses on stringent and comprehensive resource controls. The J Kernel is structured ....

....distributed garbage collection techniques are used to safely maintain sharing information. 4.3 Alta Alta [44] is an extended Java Virtual Machine that provides a hierarchical process model and system API modeled after that provided by the Fluke microkernel. Fluke supports a nested process model [22], in which a process can manage all of the resources of child processes in much the same way that an operating system manages the resources of its processes. Memory management and CPU accounting are explicitly supported by the Alta system API. Higher level services, such as network access and file ....

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proc. of the Second Symposium on Operating Systems Design and Implementation, pages 137--151. USENIX Association, Oct. 1996.

No context found.

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In USENIX, editor, 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), October 28--31, 1996.

No context found.

B. Ford and M. H. et al. Microkernels meet recursive virtual machines. In Operating Systems Design and Implementation, pages 137--151, 1996.

No context found.

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, S. Goel, and S. Clawson, Microkernels Meet Recursive Virtual Machines, Tech. Rep. UUCS-96-004, Department of Computer Science, University of Utah, May 1996.

No context found.

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels Meet Recursive Virtual Machines. In Proceedings of the 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), Seattle, WA, Oct 1996.

No context found.

Ford, Bryan, Mike Hibler, Jay Lepreau, Patrick Tullmann, Godmar Back and Stephen Clawson. Microkernels meet recursive virtual machines. In Operating Systems Design and Implementation, pages 137--151, 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullman, Godmar Back, and Steven Clawson. Microkernels Meet Recursive Virtual Machines. In Proceedings of the 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), Seattle, WA, Oct 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullman, Godmar Back, and Stephen Clawson. Microkernels meet recursive virtual machines. In Proceedings of the Second Symposium on Operating Systems Design and Implementation (OSDI '96), pages 137--151, Seattle, Washington, October 1996.

No context found.

B. Ford et al. Microkernels meet recursive virtual machines. In Proceedings of the Second Symposium October 1996.

No context found.

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In Proceedings of the 2nd USENIX Symposium on Operating Systems Design and Implementation, pages 137--151, October 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullman, Godmar Back, and Steven Clawson. Microkernels Meet Recursive Virtual Machines. In Proceedings of the 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), Seattle, WA, Oct 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullmann, Godmar Back, Shantanu Goel, and Steven Clawson. Microkernels meet recursive virtual machines. In Proceedings of the Second Symposium on Operating Systems Design and Implementation, October 1996.

No context found.

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels Meet Recursive Virtual Machines. In Proceedings of the 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), Seattle, WA, Oct 1996.

No context found.

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels Meet Recursive Virtual Machines. In Proceedings of the 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), Seattle, WA, Oct 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullmann, Godmar Back, and Stephen Clawson. Microkernels meet recursive virtual machines. In Implementation, pages 137--151, October 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullman, Godmar Back, and Steven Clawson. Microkernels Meet Recursive Virtual Machines. In Proceedings of the 2nd USENIX Symposium on Operating Systems Design and Implementation, October 1996. 100

No context found.

B. Ford, M. Hibler, J. Lepreau, P. Tullmann, G. Back, and S. Clawson, "Microkernels Meet Recursive Virtual Machines," Proc. of USENIX Symposium on Operating Systems Design and Implementation," Oct. 1996.

No context found.

B. Ford, M. Hibler, J. Lepreau, P. Tullman, G. Back, and S. Clawson. Microkernels meet recursive virtual machines. In USENIX, editor, 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), October 28-31, 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullmann, Godmar Back, and Stephen Clawson. Microkernels meet recursive virtual machines. In Proceedings of the 1996 Symposium on Operating Systems Design and Implementation, pages 137--151, October 1996.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullman, Godmar Back, and Steven Clawson. Microkernels meet recursive virtual machines. In USENIX, editor, 2nd Symposium on Operating Systems Design and Implementation (OSDI '96), October 28-31, 1996. Seattle, WA, pages 137-151, Berkeley, CA, USA, October 1996. USENIX.

No context found.

Bryan Ford, Mike Hibler, Jay Lepreau, Patrick Tullmann, Godmar Back, and Stephen Clawson. Microkernels meet recursive virtual machines. In Proceedings of the 1996 Symposium on Operating Systems Design and Implementation, pages 137--151, October 1996.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC