2020
DOI: 10.1109/tcad.2020.3012647
|View full text |Cite
|
Sign up to set email alerts
|

eWASM: Practical Software Fault Isolation for Reliable Embedded Devices

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 16 publications
(5 citation statements)
references
References 15 publications
0
5
0
Order By: Relevance
“…Classic approaches to provide isolation and implement reliable systems on low-end embedded devices have been evolving from constructive (language/compiler-based) memory protection [58]- [62] and hardware-enforced RTOS mechanisms [21], [63], [64], to lightweight virtualization infrastructures [4], [5], [65], [66]. Tock [59] leverages limited hardware protection mechanisms as well as the type-safety features of the Rust programming language to provide a reliable multiprogramming environment for MCUs.…”
Section: Reliable Systems For Mcu-powered Iot Devicesmentioning
confidence: 99%
See 1 more Smart Citation
“…Classic approaches to provide isolation and implement reliable systems on low-end embedded devices have been evolving from constructive (language/compiler-based) memory protection [58]- [62] and hardware-enforced RTOS mechanisms [21], [63], [64], to lightweight virtualization infrastructures [4], [5], [65], [66]. Tock [59] leverages limited hardware protection mechanisms as well as the type-safety features of the Rust programming language to provide a reliable multiprogramming environment for MCUs.…”
Section: Reliable Systems For Mcu-powered Iot Devicesmentioning
confidence: 99%
“…EPOXY [60] proposes a technique called privilege overlaying and uXOM [61] implements a protection mechanism that leverages the LLVM compiler to translate all memory instructions into unprivileged ones, constraining the code region using the MPU available on Cortex-M MCUs. Peach et al proposed eWASM [62], a runtime environment to constrain memory accesses and control flow, enabled by the aWsm compiler. Several widespread embedded (RT)OSes such as Mbed OS [67], FreeRTOS [68], and Zephyr [69] have already upstream support for task isolation using the MPU.…”
Section: Reliable Systems For Mcu-powered Iot Devicesmentioning
confidence: 99%
“…Reliable systems for the IoT. Classic approaches to provide isolation and implement reliable systems on resourceconstrained devices have been evolving from constructive (language/compiler-based) memory protection [52]- [56] and hardware-enforced RTOS mechanisms [21], [57], [58], to lightweight virtualization infrastructures [5], [6], [59], [60]. Tock [53] leverages limited hardware protection mechanisms as well as the type-safety features of the Rust programming language to provide a reliable multiprogramming environment for MCUs.…”
Section: Related Workmentioning
confidence: 99%
“…EPOXY [54] proposes a technique called privilege overlaying and uXOM [55] implements a protection mechanism that leverages the LLVM compiler to translate all memory instructions into unprivileged ones, constraining the code region using the MPU available on Cortex-M MCUs. In [56], Peach et al propose eWASM, which is a runtime to constrain memory accesses and control flow, enabled by the aWsm compiler. Several widespread embedded (RT)OSes such as Mbed OS [61], FreeRTOS [62], and Zephyr [63] have already upstream support for task isolation using the MPU.…”
Section: Related Workmentioning
confidence: 99%
“…Consequently, WebAssembly modules can be executed with close to native performance in many scenarios (Jangda et al 2019). The narrow instruction set also allows the implementation of lightweight interpreters for execution on small, resource-constrained devices (Peach et al 2020).…”
Section: Webassembly Bytecodementioning
confidence: 99%