; ---------------------------------------------------------------------
; To submit, log into grace.umd.edu and use the following command:
; 	<PATH>/submit 2015 fall <COLLEGE> <COURSE> 0101 11 os_protection_mechanisms.bib
; ---------------------------------------------------------------------



; Required Readings

@INPROCEEDINGS{ Wahbe93,
  title        = {Efficient Software-Based Fault Isolation},
  author       = {Robert Wahbe and Steven Lucco and Thomas E. Anderson and Susan L. Graham},
  booktitle    = {Proceedings of the Fourteenth {ACM} Symposium on Operating System Principles, {SOSP} 1993, The Grove Park Inn and Country Club, Asheville, North Carolina, USA, December 5-8, 1993},
  bdsk-url-2   = {http://dx.doi.org/10.1145/168619.168635},
  bibsource    = {dblp computer science bibliography, http://dblp.org},
  timestamp    = {Mon, 22 Jun 2015 17:24:50 +0200},
  url          = {http://doi.acm.org/10.1145/168619.168635},
  doi          = {10.1145/168619.168635},
  crossref     = {DBLP:conf/sosp/1993},
  abstract     = {One way to provide fault isolation among cooperating software modules is to place each in its own address space. However, for tightly-coupled modules, this solution incurs prohibitive context switch overhead. In this paper, we present a software approach to implementing fault isolation within a single address space.Our approach has two parts. First, we load the code and data for a distrusted module into its own fault do main, a logically separate portion of the application's address space. Second, we modify the object code of a distrusted module to prevent it from writing or jumping to an address outside its fault domain. Both these software operations are portable and programming language independent.Our approach poses a tradeoff relative to hardware fault isolation: substantially faster communication between fault domains, at a cost of slightly increased execution time for distrusted modules. We demonstrate that for frequently communicating modules, implementing fault isolation in software rather than hardware can substantially improve end-to-end application performance.},
  year         = {1993},
  pages        = {203--216},

  studentfirstname ="",
  studentlastname ="",
  summary =	 "",
  contribution1 ="",
  contribution2 ="",
  contribution3 ="",
  contribution4 ="",
  contribution5 ="",
  weakness1 =	 "",
  weakness2 =	 "",
  weakness3 =	 "",
  weakness4 =	 "",
  weakness5 =	 "",
  interesting =	 "high/med/low",
  opinions =	 "",
}


; BibTex cross-references (don't add anything here)

@PROCEEDINGS{ DBLP:conf/sosp/1993,
  title        = {Proceedings of the Fourteenth {ACM} Symposium on Operating System Principles, {SOSP} 1993, The Grove Park Inn and Country Club, Asheville, North Carolina, USA, December 5-8, 1993},
  bdsk-url-2   = {http://dx.doi.org/10.1145/168619},
  bibsource    = {dblp computer science bibliography, http://dblp.org},
  timestamp    = {Mon, 22 Jun 2015 17:24:50 +0200},
  editor       = {Andrew P. Black and Barbara Liskov},
  url          = {http://doi.acm.org/10.1145/168619},
  isbn         = {0-89791-632-8},
  publisher    = {{ACM}},
  doi          = {10.1145/168619},
  year         = {1993},
}