604:
54:
In a traditional OS with private per-process address space, memory protection is based on address space boundaries ("address space isolation"). Single address-space operating systems make translation and protection orthogonal, which in no way weakens protection. The core advantage is that pointers
81:, which provides no address translation and generally no memory protection. In contrast, a SASOS makes protection orthogonal to translation: it may be possible to name a data item (i.e. know its virtual address) while not being able to access it.
55:(i.e. memory references) have global validity, meaning their meaning is independent of the process using it. This allows sharing pointer-connected data structures across processes, and making them persistent, i.e. storing them on backup store.
62:
have direct support for protection independent of translation. On such architectures, a SASOS may be able to perform context switches faster than a traditional OS. Such architectures include
535:
574:
Eric J. Koldinger; Jeffrey S. Chase; Susan J. Eggers (September 1992). "Architecture support for single address space operating systems".
242:
Eric J. Koldinger; Jeffrey S. Chase; Susan J. Eggers (September 1992). "Architecture support for single address space operating systems".
523:
645:
543:
Michael M. Swift; Brian N. Bershad; Henry M. Levy (December 2003). "Improving the reliability of commodity operating systems".
497:
320:
669:
357:
619:
450:
304:
165:
435:. quote: "Torsion ... a single address space multitasking operating system with transparent data persistence."
59:
144:
638:
71:
664:
197:
149:
514:
471:
334:
288:
129:
119:
557:
88:
67:
448:
302:
631:
552:
509:
466:
403:
329:
283:
271:
Tim
Wilkinson; Kevin Murray; Stephen Russell; Gernot Heiser; Jochen Liedt (13 November 1995).
420:
377:
154:
611:
312:
8:
244:
124:
40:
527:
454:
308:
272:
457:(November 1994). "Sharing and protection in a single-address-space operating system".
401:
388:
270:
217:
78:
531:
583:
562:
519:
476:
365:
361:
339:
253:
32:
20:
48:
573:
378:"CHERI: a research platform deconflating hardware virtualization and protection"
241:
109:
615:
493:
373:
222:
44:
658:
542:
489:
192:
36:
524:
10.1002/(SICI)1097-024X(19980725)28:9<901::AID-SPE181>3.0.CO;2-7
140:
Related are OSes that provide protection through language-level type safety
566:
421:"Theseus: an Experiment in Operating System Structure and State Management"
587:
480:
343:
257:
202:
170:
99:
369:
207:
160:
84:
SASOS projects using hardware-based protection include the following:
212:
187:
43:. In a single address space operating system, numerically identical (
385:
Unpublished workshop paper for RESoLVE’12, March 3, 2012, London, UK
313:"Sharing and protection in a single-address-space operating system"
51:
in different processes all refer to exactly the same byte of data.
402:
Michael Golm; Meik Felser; Christian
Wawersich; Jürgen Kleinöder.
488:
432:
134:
63:
603:
376:; Paeps, Philip; Roe, Michael; Saidi, Hassen (3 March 2012).
356:
113:
103:
93:
492:; Elphinstone, Kevin; Vochteloo, Jerry; Russell, Stephen;
175:
419:
Kevin Boos, Namitha
Liyanage, Ramla Ijaz, and Lin Zhong.
498:"The Mungi Single-Address-Space Operating System"
656:
639:
646:
632:
364:; Woodruff, Jonathan; Anderson, Jonathan;
556:
513:
470:
333:
287:
273:"Single Address Space Operating Systems"
35:that provides only one globally shared
657:
77:A SASOS should not be confused with a
25:single address space operating system
598:
459:ACM Transactions on Computer Systems
321:ACM Transactions on Computer Systems
296:
264:
545:ACM SIGOPS Operating Systems Review
538:from the original on June 27, 2022.
13:
282:. Section 2: "Memory Protection".
14:
681:
502:Software: Practice and Experience
602:
442:
16:Operating system classification
426:
413:
395:
350:
235:
1:
280:University of New South Wales
228:
618:. You can help Knowledge by
391:Computer Science Laboratory.
7:
181:
10:
686:
670:Computer engineering stubs
597:
433:"Torsion Operating System"
404:"The JX Operating System"
96:(formerly called OS/400)
72:capability architectures
66:, and Version 5 of the
60:processor architectures
614:-related article is a
567:10.1145/1165389.945466
588:10.1145/143371.143508
481:10.1145/195792.195795
453:; Michael J. Feeley;
344:10.1145/195792.195795
307:; Michael J. Feeley;
258:10.1145/143371.143508
612:computer-engineering
358:Watson, Robert N. M.
576:ACM SIGPLAN Notices
372:; Moore, Simon W.;
245:ACM SIGPLAN Notices
455:Edward D. Lazowska
449:Jeffrey S. Chase;
374:Murdoch, Steven J.
309:Edward D. Lazowska
303:Jeffrey S. Chase;
157:a research Java OS
665:Operating systems
627:
626:
389:SRI International
362:Neumann, Peter G.
311:(November 1994).
218:Flat memory model
79:flat memory model
49:logical addresses
677:
648:
641:
634:
606:
599:
591:
570:
560:
539:
517:
484:
474:
436:
430:
424:
417:
411:
410:
408:
399:
393:
392:
382:
354:
348:
347:
337:
317:
300:
294:
293:
291:
277:
268:
262:
261:
239:
68:Arm architecture
33:operating system
21:computer science
685:
684:
680:
679:
678:
676:
675:
674:
655:
654:
653:
652:
595:
515:10.1.1.146.4216
494:Liedtke, Jochen
472:10.1.1.127.7313
445:
440:
439:
431:
427:
418:
414:
406:
400:
396:
380:
368:; Dave, Nirav;
355:
351:
335:10.1.1.127.7313
315:
301:
297:
275:
269:
265:
240:
236:
231:
184:
74:such as CHERI.
17:
12:
11:
5:
683:
673:
672:
667:
651:
650:
643:
636:
628:
625:
624:
607:
593:
592:
582:(9): 175–186.
571:
540:
508:(9): 901–928.
490:Heiser, Gernot
486:
465:(4): 271–307.
444:
441:
438:
437:
425:
412:
394:
366:Anderson, Ross
349:
328:(4): 271–307.
295:
289:10.1.1.13.7042
263:
252:(9): 175–186.
233:
232:
230:
227:
226:
225:
223:Virtual memory
220:
215:
210:
205:
200:
195:
190:
183:
180:
179:
178:
173:
168:
163:
158:
152:
147:
138:
137:
132:
127:
122:
117:
107:
97:
91:
45:virtual memory
15:
9:
6:
4:
3:
2:
682:
671:
668:
666:
663:
662:
660:
649:
644:
642:
637:
635:
630:
629:
623:
621:
617:
613:
608:
605:
601:
600:
596:
589:
585:
581:
577:
572:
568:
564:
559:
558:10.1.1.5.3338
554:
550:
546:
541:
537:
533:
529:
525:
521:
516:
511:
507:
503:
499:
495:
491:
487:
482:
478:
473:
468:
464:
460:
456:
452:
451:Henry M. Levy
447:
446:
434:
429:
422:
416:
405:
398:
390:
386:
379:
375:
371:
367:
363:
359:
353:
345:
341:
336:
331:
327:
323:
322:
314:
310:
306:
305:Henry M. Levy
299:
290:
285:
281:
274:
267:
259:
255:
251:
247:
246:
238:
234:
224:
221:
219:
216:
214:
211:
209:
206:
204:
201:
199:
196:
194:
193:Hybrid kernel
191:
189:
186:
185:
177:
174:
172:
169:
167:
164:
162:
159:
156:
153:
151:
148:
146:
143:
142:
141:
136:
133:
131:
128:
126:
123:
121:
118:
115:
111:
108:
105:
101:
98:
95:
92:
90:
87:
86:
85:
82:
80:
75:
73:
70:, as well as
69:
65:
61:
56:
52:
50:
46:
42:
38:
37:address space
34:
30:
26:
22:
620:expanding it
609:
594:
579:
575:
548:
544:
505:
501:
462:
458:
443:Bibliography
428:
415:
397:
384:
352:
325:
319:
298:
279:
266:
249:
243:
237:
139:
83:
76:
57:
53:
28:
24:
18:
370:Laurie, Ben
203:Microkernel
166:Singularity
116:, Australia
106:, Australia
659:Categories
551:(5): 207.
229:References
208:Nanokernel
171:Theseus OS
161:Phantom OS
553:CiteSeerX
510:CiteSeerX
467:CiteSeerX
330:CiteSeerX
284:CiteSeerX
213:Unikernel
188:Exokernel
41:processes
536:Archived
532:62189930
496:(1998).
182:See also
135:Sombrero
39:for all
31:) is an
423:. 2020.
176:Torsion
120:Nemesis
64:Itanium
555:
530:
512:
469:
332:
286:
198:Kernel
150:Genera
100:Iguana
610:This
528:S2CID
407:(PDF)
381:(PDF)
316:(PDF)
276:(PDF)
130:Scout
114:NICTA
110:Mungi
104:NICTA
94:IBM i
89:Angel
58:Some
29:SASOS
616:stub
145:Br1X
125:Opal
27:(or
23:, a
584:doi
563:doi
520:doi
477:doi
340:doi
254:doi
112:at
102:at
19:In
661::
580:27
578:.
561:.
549:37
547:.
534:.
526:.
518:.
506:28
504:.
500:.
475:.
463:12
461:.
387:.
383:.
360:;
338:.
326:12
324:.
318:.
278:.
250:27
248:.
155:JX
47:)
647:e
640:t
633:v
622:.
590:.
586::
569:.
565::
522::
485:.
483:.
479::
409:.
346:.
342::
292:.
260:.
256::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.