Details
| Original language | English |
|---|---|
| Title of host publication | PLOS '07: Proceedings of the 4th workshop on Programming languages and operating systems |
| Publication status | Published - Oct 2007 |
| Externally published | Yes |
| Event | 4th Workshop on Programming Languages and Operating Systems, PLOS 2007 - Stevenson, WA, United States Duration: 18 Oct 2007 → 18 Oct 2007 |
Abstract
We describe the implementation of memory protection by means of aspect-oriented programming (AOP) in CiAO, an AUTOSAR-like family of embedded operating systems. The use of AOP was originally motivated by the fact that memory protection is a cross-cutting policy, which, furthermore, has to be configurable at build-time in AUTOSAR. We learned, however, that besides switching between full protection and no protection, an AOP-based approach also makes it easy to apply completely different models of protection. For the domain of statically configured embedded systems, where certain failure scenarios can often be excluded by means of code analysis or even probability, this facilitates tailored and light-weight "nav-as-vou-use" protection strateaies
Keywords
- Aspect-aware operating system, Aspect-oriented programming (AOP), AspectC++, CiAO, Configurability, Memory protection
ASJC Scopus subject areas
- Computer Science(all)
- Software
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
PLOS '07: Proceedings of the 4th workshop on Programming languages and operating systems. 2007. 3.
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
TY - GEN
T1 - Configurable Memory Protection by Aspects
AU - Lohmann, Daniel
AU - Streicher, Jochen
AU - Hofer, Wanja
AU - Spinczyk, Olaf
AU - Schröder-Preikschat, Wolfgang
PY - 2007/10
Y1 - 2007/10
N2 - We describe the implementation of memory protection by means of aspect-oriented programming (AOP) in CiAO, an AUTOSAR-like family of embedded operating systems. The use of AOP was originally motivated by the fact that memory protection is a cross-cutting policy, which, furthermore, has to be configurable at build-time in AUTOSAR. We learned, however, that besides switching between full protection and no protection, an AOP-based approach also makes it easy to apply completely different models of protection. For the domain of statically configured embedded systems, where certain failure scenarios can often be excluded by means of code analysis or even probability, this facilitates tailored and light-weight "nav-as-vou-use" protection strateaies
AB - We describe the implementation of memory protection by means of aspect-oriented programming (AOP) in CiAO, an AUTOSAR-like family of embedded operating systems. The use of AOP was originally motivated by the fact that memory protection is a cross-cutting policy, which, furthermore, has to be configurable at build-time in AUTOSAR. We learned, however, that besides switching between full protection and no protection, an AOP-based approach also makes it easy to apply completely different models of protection. For the domain of statically configured embedded systems, where certain failure scenarios can often be excluded by means of code analysis or even probability, this facilitates tailored and light-weight "nav-as-vou-use" protection strateaies
KW - Aspect-aware operating system
KW - Aspect-oriented programming (AOP)
KW - AspectC++
KW - CiAO
KW - Configurability
KW - Memory protection
UR - http://www.scopus.com/inward/record.url?scp=37149043907&partnerID=8YFLogxK
U2 - 10.1145/1376789.1376794
DO - 10.1145/1376789.1376794
M3 - Conference contribution
AN - SCOPUS:37149043907
SN - 9781595939227
BT - PLOS '07: Proceedings of the 4th workshop on Programming languages and operating systems
T2 - 4th Workshop on Programming Languages and Operating Systems, PLOS 2007
Y2 - 18 October 2007 through 18 October 2007
ER -