Small virtual machines: A survey

ABSTRACT

It has been demonstrated that virtual machines can be successfully implemented on large computer systems. They can also be implemented on small computer systems (“mini-computers”). The paper will show this, and at the same time discuss the various architectural features by which virtual machine implementation is achieved. Examining features which make machines “small”, we find architectural limitations. These machines are usually byte or word addressable where the virtual address space bound is the word size. They usually rely on indexing and indirect addressing. Most instructions are one word long. The instruction repetoire is not particularly rich. There is a simple I/O structure with facilities for hardware interrupts and direct memory access (block I/O transfers). In summary, small virtual machines are effective for software development of systems having one or more of the following characteristics: • shared facilities • no common operating system • user I/O programming •communications control •process control •fictitious I/O devices

REFERENCES

• 1: Data General Corporation, "How to Use the Nova Computers", Publication #NM-5, Southboro, Mass., 1971.
• 2: Data General Corporation, "Technical Reference - 8021 Memory Management and Protection Unit," Publication #014-000019-00, Southboro, Mass., 1973.
• 3: Digital Equipment Corporation, "PDP 8/e and PDP 8/m Small Computer Handbook," Publication #082X-01071-A1589 D-09-100, Maynard, Mass., 1972.
• 4: Digital Equipment Corporation, "PDP 11/45 Processor Handbook," Publication #112-01071-1876 D-09-15, Maynard, Mass., 1971.
• 5: Gagliardi, U.O. and Goldberg, R.P., "Virtualizable Architectures", Proceedings of the 1972 ACM International Computing Symposium, Venice, Italy, April, 1972, pp. 527-538.
• 6: S. W. Galley, PDP-10 virtual machines, Proceedings of the workshop on virtual computer systems, p.30-34, March 26-27, 1973, Cambridge, Massachusetts, United States [doi>10.1145/800122.803947]
• 7: General Automation, Inc., "Reference Manual for SPC-16 Automation Computers", Publication #88A00243A-B, Anaheim, California.
• 8: Goldberg, R. P., "Architectural Principles for Virtual Computer Systems", Report #24-72, Center for Research in Computing Technology, Harvard University, Cambridge, Mass.
• 9: Hewlett-Packard Company, "HP 3000 Computer System Reference Manual", Publication #03000-90019, Cupertino, California, 1972.
• 10: Honeywell Information Systems, "Honeywell System 700 Programmers' Reference Manual", Document #70130072575A, Waltham, Mass., 1972.
• 11: IBM Corporation, "Program Information Department," Control Program-67/Cambridge Monitor System, Type III Release #360 D-05.2. 005, Hawthorne, New York.
• 12: Interdata, Inc., 1971, "Model 70 User's Manual", Publication #29-261, Oceanport, New Jersey, 1971.
• 13: Lauer, H.C. and Snow, C.R., "Is Supervisor-state Necessary", International Computing Symposium Proceedings, Venice, Italy, April 1972, pp. 293-301.
• 14: Systems Engineering Laboratories, "Systems 72 Computer Reference Manual," Publication #301-720005-001, Ft. Lauderdale, Florida, 1972.
• 15: Varian Data Machines, "Varian 73 System Handbook," Publication #98-A-9906-010, Irvine, California, 1972.
• 16: Xerox Data Systems, "Sigma 2 Computer Reference Manual," Publication #90-09-64D, El Segundo, California, 1968.

INDEX TERMS

Primary Classification:
  D. Software
  D.4 OPERATING SYSTEMS
      D.4.2 Storage Management
          Subjects: Virtual memory

Additional Classification:
  D. Software
  D.4 OPERATING SYSTEMS
      D.4.1 Process Management
          Subjects: Multiprocessing/multiprogramming/multitasking
      D.4.8 Performance

General Terms:
Design, Management, Performance