128-Bit Addressing in RISC-V and Security

More documents

Recommendations

Info

Background • Other’s (pioneer’s) did not simply add more bits – IBM – FS (Ref: [13]) – 1976 • Tagged 16 byte pointers (CapabiliCes) • System/38 is the diminuCve of FS – Data General - FHP (Ref: [3, 4,17]) - 1980 • Ref: hgp://people.cs.clemson.edu/ ~mark/ip.html – true object orientaCon with onelevel addressing across a network (128 bit pointers!) – Intel 432 iMAX OS – (Ref: [16]) – 1980 • 24 bit passive address • 80 bit UID (16 bit checksum) 2016 _NOV _RISCV_WORKSHOP 4
What Happened • MulCcs at MIT – UNIX is the diminuCve of MulCcs • Project Genie at UC Berkeley • Influenced Industry – Graduates – A new era of compuCng – Technology was not ready 2016 _NOV _RISCV_WORKSHOP 5
Page 1 and 2: 128-Bit Addressing in RISC-V and Se
Page 3: Background • Since the late 70’
Page 7 and 8: Going Forward • There Time is to
Page 9 and 10: ProtecCon ObjecCves • The origina
Page 11 and 12: Previous Efforts • Another soluCo
Page 13 and 14: Strawman - RV128I OBJECT ID Byte Of
Page 15 and 16: What is a Object ? • A Object is
Page 17 and 18: AuthenCcaCon • The address space
Page 19 and 20: Memory Management • Each object c
Page 21 and 22: 64 BIT LINUX -Memory Management Pro
Page 23 and 24: Exascale Issues • Subject to cost
Page 25 and 26: 128- BIT VIRTUAL ADDRESSING -Protec
Page 27 and 28: ACL (Access Control List) - ENTRY P
Page 29 and 30: REFERENCE MONITOR • It must valid
Page 31 and 32: Summary • Compare to CHERI [12] -
Page 33 and 34: References • [12] Robert N.M. Wat
Page 35 and 36: RevocaCon • Every client has a
Page 37 and 38: Some Object UID Math • 60 seconds
Page 39 and 40: ProtecCon in Unified Name Space •
Page 41: Shadow Stack - Architecture Return

128-Bit Addressing in RISC-V and Security

Create successful ePaper yourself

Delete template?

Save as template?