1994
DOI: 10.1145/195470.195579
|View full text |Cite
|
Sign up to set email alerts
|

Hardware support for fast capability-based addressing

Abstract: Traditional methods of providing protection in memory systems do so at the cost of increased context switch time and/or increased storage to record access permissions for processes. With the advent of computers that supported cycle-by-cycle multithreading, protection schemes that increase the time to perform a context switch are unacceptable, but protecting unrelated processes from each other is still necessary if such machines are to be used in non-trusting environments. This paper exam… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
16
0

Year Published

2000
2000
2019
2019

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 26 publications
(16 citation statements)
references
References 14 publications
0
16
0
Order By: Relevance
“…It is possible to implement a memory capability model in a strict RISC instruction set with a load-store architecture and single-cycle operations as demonstrated by the M-Machine [5]. In a RISC implementation, memory capabilities can be stored in registers or in memory, but must be loaded into registers for use.…”
Section: A Risc Memory Capability Modelmentioning
confidence: 99%
See 2 more Smart Citations
“…It is possible to implement a memory capability model in a strict RISC instruction set with a load-store architecture and single-cycle operations as demonstrated by the M-Machine [5]. In a RISC implementation, memory capabilities can be stored in registers or in memory, but must be loaded into registers for use.…”
Section: A Risc Memory Capability Modelmentioning
confidence: 99%
“…The M-Machine [5] is a 64-bit tagged-memory capability sys tem design using guarded pointers to implement fine-grained memory protection for pointer safety. M-Machine pointers are unforgeable.…”
Section: M-machinementioning
confidence: 99%
See 1 more Smart Citation
“…Other hardware systems have implemented similar constructs, e.g., the 64-bit guarded pointers [8] of Carter, et al, avoid translation tables by encoding permission bits and segment sizes in the pointer itself. This allows lightweight (cycle-by-cycle) context switches, allowing instructions from different threads with different security domains to be mixed in a processor pipeline and encouraging more fine-grained separation of privilege domains.…”
Section: Object Capabilitiesmentioning
confidence: 99%
“…With the above assumptions, we can represent the pointer and its base and bound with an overhead of only |B| bits, which is, at most, the log of the size of the address space. This is the scheme used for guarded pointers by Carter [8] and for the Baggy Bounds software scheme [2].…”
Section: Aligned Encodingmentioning
confidence: 99%