An experimental implementation of the kernel/domain architecture

Spier, Michale J.; Hastings, T.; Cutler, David N.

doi:10.1145/800009.808043

Cited by 13 publications

(3 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The architecture can be termed a domain architecture [18], since every procedure is encapsulated within a private memory space. One of the object types in the architecture is the module.…”

Section: The Sward Architecturementioning

confidence: 99%

A hardware implementation of capability-based addressing

Myers¹,

Buckingham²

1980

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

The SWARD architecture, an experimental higher-level architecture, contains the naming and protection concept of capability-based addressing. After discussing the merits of capability-based addressing, its general representation in the SWARD architecture is discussed. The initial representation of capability-based addressing in the architecture led to a set of problems; these problems are described, as well as their solutions. Finally, the implementation of capabilities by the processor is discussed.

show abstract

“…The architecture can be termed a domain architecture [18], since every procedure is encapsulated within a private memory space. One of the object types in the architecture is the module.…”

Section: The Sward Architecturementioning

confidence: 99%

A hardware implementation of capability-based addressing

Myers¹,

Buckingham²

1980

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

show abstract

“…The policy algorithm, however, could never read or write the contents of pages, learn the segment to which each page belonged, or cause one page to overwrite (10) Separation of policy from mechanism is a structural principle that has been explored by many others [21,22,23].…”

Section: The Security Kernelmentioning

confidence: 99%

Engineering a security kernel for Multics

Schroeder¹

1975

Proceedings of the Fifth Symposium on Operating Systems Principles - SOSP '75

View full text Add to dashboard Cite

This paper describes a research project to engineer a security kernel for Multics, a general-purpose, remotely accessed, multiuser computer system.The goals are to identify the minimum mechanism that must be correct to guarantee computer enforcement of desired constraints on information access, to simplify the structure of that minimum mechanism to make verification of correctness by auditing possible, and to demonstrate by test'implementation that the security kernel so developed is capable of supporting the functionality of Multics completely and efficiently.The paper presents the overall viewpoint and plan for the project and discusses initial strategies being employed to define and structure the security kernel.

show abstract

“…The nature of OS architecture and of verification-based program synthesis suggests that a synthesis-based approach might reduce porting costs and/or provide an efficient way to produce verified operating system ports. Most OSes are structured to be portable as shown in Figure 1; they have clearly delineated machine-independent (top box in dark gray) and machine-dependent parts (middle boxes in light gray) [Custer 1992;Love 2010;McKusick et al 1996;Rashid et al 1987;Spier et al 1973]. Porting an OS requires re-implementing the machine-dependent parts (light gray boxes in Figure 1), not performing deep structural reorganization.…”

Section: Introductionmentioning

confidence: 99%

Towards Porting Operating Systems with Program Synthesis

Hu,

Lu,

Holland

et al. 2022

Preprint

View full text Add to dashboard Cite

The end of Moore's Law has ushered in a diversity of hardware not seen in decades. Operating system (and system software) portability is accordingly becoming increasingly critical. Simultaneously, there has been tremendous progress in program synthesis. We set out to explore the feasibility of using modern program synthesis to generate the machine-dependent parts of an operating system. Our ultimate goal is to generate new ports automatically from descriptions of new machines.One of the issues involved is writing specifications, both for machine-dependent operating system functionality and for instruction set architectures. We designed two domain-specific languages: Alewife for machine-independent specifications of machine-dependent operating system functionality, and Cassiopea for describing instruction set architecture semantics. Automated porting also requires an implementation. We developed a toolchain that, given an Alewife specification and a Cassiopea machine description, specializes the machine-independent specification to the target instruction set architecture and synthesizes an implementation in assembly language. Using this approach, we demonstrate successful synthesis of a total of 140 OS components from two pre-existing OSes for four real hardware platforms. We also developed several optimization methods for OS-related assembly synthesis to improve scalability.The effectiveness of our languages and ability to synthesize code for all 140 specifications is evidence of the feasibility of program synthesis for machine-dependent OS code. However, many research challenges remain; we also discuss the benefits and limitations of our synthesis-based approach to automated OS porting.CCS Concepts: • Software and its engineering → General programming languages; Formal methods; Assembly languages; Domain specific languages.

show abstract

An experimental implementation of the kernel/domain architecture

Cited by 13 publications

References 19 publications

A hardware implementation of capability-based addressing

A hardware implementation of capability-based addressing

Engineering a security kernel for Multics

Towards Porting Operating Systems with Program Synthesis

Contact Info

Product

Resources

About