Nothing Special   »   [go: up one dir, main page]
Skip to main content
We gratefully acknowledge support from the Simons Foundation, member institutions, and all contributors. Donate
arXiv logo
Cornell University Logo

Computer Science > Operating Systems

arXiv:1703.06571 (cs)
[Submitted on 20 Mar 2017]

Title:Formalizing Memory Accesses and Interrupts

Authors:Reto Achermann (Systems Group, Department of Computer Science, ETH Zurich), Lukas Humbel (Systems Group, Department of Computer Science, ETH Zurich), David Cock (Systems Group, Department of Computer Science, ETH Zurich), Timothy Roscoe (Systems Group, Department of Computer Science, ETH Zurich)
View PDF
Abstract:The hardware/software boundary in modern heterogeneous multicore computers is increasingly complex, and diverse across different platforms. A single memory access by a core or DMA engine traverses multiple hardware translation and caching steps, and the destination memory cell or register often appears at different physical addresses for different cores. Interrupts pass through a complex topology of interrupt controllers and remappers before delivery to one or more cores, each with specific constraints on their configurations. System software must not only correctly understand the specific hardware at hand, but also configure it appropriately at runtime. We propose a formal model of address spaces and resources in a system that allows us to express and verify invariants of the system's runtime configuration, and illustrate (and motivate) it with several real platforms we have encountered in the process of OS implementation.
Comments: In Proceedings MARS 2017, arXiv:1703.05812
Subjects: Operating Systems (cs.OS); Hardware Architecture (cs.AR)
ACM classes: D.4; D.4.2; D.4.7; D.3.4
Cite as: arXiv:1703.06571 [cs.OS]
  (or arXiv:1703.06571v1 [cs.OS] for this version)
  https://doi.org/10.48550/arXiv.1703.06571
Journal reference: EPTCS 244, 2017, pp. 66-116
Related DOI: https://doi.org/10.4204/EPTCS.244.4

Submission history

From: EPTCS [view email] [via EPTCS proxy]
[v1] Mon, 20 Mar 2017 02:47:57 UTC (119 KB)
Full-text links:

Access Paper:

  • View PDF
  • TeX Source
  • Other Formats
view license
Current browse context:
cs.OS
< prev   |   next >
new | recent | 2017-03
Change to browse by:
cs
cs.AR

References & Citations

export BibTeX citation

Bookmark

BibSonomy logo Reddit logo

Bibliographic and Citation Tools

Bibliographic Explorer (What is the Explorer?)
Connected Papers (What is Connected Papers?)
Litmaps (What is Litmaps?)
scite Smart Citations (What are Smart Citations?)

Code, Data and Media Associated with this Article

alphaXiv (What is alphaXiv?)
CatalyzeX Code Finder for Papers (What is CatalyzeX?)
DagsHub (What is DagsHub?)
Gotit.pub (What is GotitPub?)
Hugging Face (What is Huggingface?)
Papers with Code (What is Papers with Code?)
ScienceCast (What is ScienceCast?)

Demos

Replicate (What is Replicate?)
Hugging Face Spaces (What is Spaces?)
TXYZ.AI (What is TXYZ.AI?)

Recommenders and Search Tools

Influence Flower (What are Influence Flowers?)
CORE Recommender (What is CORE?)

arXivLabs: experimental projects with community collaborators

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

Which authors of this paper are endorsers? | Disable MathJax (What is MathJax?)