Advertisement

ERRIC Reliability

  • Igor SchagaevEmail author
  • Eugene Zouev
  • Kaegi Thomas
Chapter

Abstract

The key property of our design is resilience. So far we mostly covered system software methods and schemes to achieve or support it. Previous Chaps.  14 and  15 explained briefly what hardware (processor) should possess (including reduction on functions and limited in architecture options) to be able to implement resilience in the most efficient way. Here, we intend to analyze what we have achieved in hardware design in terms of malfunction tolerance—attempting to use heavy artillery of system software as less as possible, making dirty work of fault detection and determination (malfunction or permanent for hardware).

References

  1. 1.
    Blaeser L, Monkman S, Schagaev I (2014) Evolving systems. In: Proceedings of the World Comp’14, USA, July 14. https://www.academia.edu/7685575/Evolving_systems_-_WorldComp_2014
  2. 2.
    Castano V, Schagaev I. Resilient computer system design. Springer. ISBN 978-3-319-15069-7Google Scholar
  3. 3.
    Intel Corporation (2009) Intel 64 and 32 architectures software developers manual, vol 1: basic architecture. Technical report 253665-032USGoogle Scholar
  4. 4.
    Intel Corporation (2004) Intel pxa255 processor developer’s manual. Technical report. Order number 278693-002, Intel Corporation, January 2004Google Scholar
  5. 5.
    ARM Limited (2005) ARM architecture reference manual. Technical report, ARM LimitedGoogle Scholar

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  1. 1.IT-ACS LtdStevenageUK
  2. 2.Department of InformaticsTechnopolisInnopolis, KazanRussia

Personalised recommendations