DOCSLIB.ORG

D4.5 Multios Integration Final.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
D4.5 Multios Integration Final.Pdf HERCULES: High-Performance Real-Time Architectures for Low-Power Embedded Systems Project title: High-Performance Real-Time Architectures for Low-Power Embedded Systems Acronym: HERCULES Project ID: 688860 Call identifier: H2020 – ICT 04-2015 – Customized and low power computing Project coordinator: Prof. Marko Bertogna, University of Modena and Reggio Emilia D4.5: Multi-OS Integration and Virtualization Document title: Multi-OS Integration and Virtualization Version: 1.3 Deliverable No.: D4.5 Lead task beneficiary: EVI Partners involved: EVI, UNIMORE, CTU Author: C. Scordino, L. Cuomo, M. Solieri, M. Sojka Status: Final Date: 2018-12-30 Nature: S Dissemination level: PU – Public D4.5: Multi-OS Integration and Virtualization Purpose & Scope Deliverable D4.5 is a package containing the software for the concurrent execution of multiple operating systems (i.e., the Real-Time Linux developed in Task 4.1 and the Lightweight Real-Time Operating System (RTOS) de- veloped in Task 4.2) on the same multi-core System-on-Chip (SoC). In addition, the software implements proper mechanisms (namely, cache colouring, memguarding and co-scheduling) to limit the interference on shared hardware resources between the different Operating Systems (OSs). This document aims at illustrating the code developed, providing information about how to configure and use the provided software. The developed source code is available in the package provided along with this document. A subset of the developed code has been also released as open-source software [JailEvi, JailTX1, JailTX2]. The remaining part will we be similarly published after the project conclusion. Revision History Version Date Author/Reviewer Comments 0.1 2018-06-21 EVI First version 0.2 2018-06-26 UNIMORE LaTeX conversion 0.3 2018-07-27 UNIMORE Revised structure, added description and guide for cache color- ing support, fixed acronyms 1.0 2018-07-29 CTU Added MemGuard description 1.1 2018-10-30 UNIMORE Extended PREM guide, general revision 1.2 2018-10-30 UNIMORE Included reviewers comments 1.3 2018-12-30 UNIMORE Final revision HERCULES project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement: 688860. This document reflects only the author’s view and the EU Commission is not responsible for any use that may be made of the information it contains. Ref: D4.5 HERCULES: Horizon 2020 project #688860 Page i D4.5: Multi-OS Integration and Virtualization Contents Acronyms 1 1 Introduction 2 1.1 Objectives .......................................... 2 2 Hypervisor 3 2.1 Introduction ......................................... 3 2.2 Hypervisor Selection ..................................... 3 2.3 Jailhouse ........................................... 4 3 Contributions 6 3.1 Porting on the Reference Platforms .............................. 6 3.2 Inter-Guest Communication Mechanism ........................... 6 3.3 Cache Coloring ........................................ 7 3.4 MemGuard .......................................... 7 3.5 Memory Co-Scheduling .................................... 8 4 User’s Guide 9 4.1 Hypervisor Installation .................................... 9 4.2 Cache Coloring Configuration ................................. 9 4.2.1 Hypervisor configuration ............................... 9 4.2.2 Preliminaries .................................... 9 4.2.3 Color Definition Configuration ............................ 10 4.2.4 Color Assignment Configuration ........................... 11 4.3 MemGuard Configuration ................................... 12 4.4 Memory Co-Scheduling Configuration ............................ 14 Ref: D4.5 HERCULES: Horizon 2020 project #688860 Page ii D4.5: Multi-OS Integration and Virtualization Acronyms API Application Program Interface . 6 ARXML AUTOSAR XML . 7 AUTOSAR AUTomotive Open System ARchitecture . 3 ECU Electronic Control Unit . 3 CPU Central Processing Unit . 4 DRAM Dynamic Random Access Memory . 14 GA Grant Agreement . 2 GPOS General-Purpose Operating System . 3 GNU GPL GNU General Public License . 4 I/O Input/Output . 5 LLC Last-Level Cache . 7 MPSoC MultiProcessor System-on-Chip . 10 PREM PReditable Execution Model . 14 OS Operating System . i OSEK/VDX Offene Systeme und deren Schnittstellen für die Elektronik in Kraftfahrzeugen / Vehicle Distributed eXecutive . 3 RAM Random-Access Memory . 4 RTE RunTime Environment . 7 RTOS Real-Time Operating System . i SDRAM Synchronous Dynamic Random-Access memory . 5 SoC System-on-Chip. .i US+ Xilinx Zinq UltraScale+. .7 Ref: D4.5 HERCULES: Horizon 2020 project #688860 Page 1 D4.5: Multi-OS Integration and Virtualization 1 Introduction 1.1 Objectives As illustrated in the Grant Agreement (GA), [Task 4.5 of HERCULES] aims at investigating, designing and developing efficient mechanisms for the concurrent execution of multiple OS on the same SoC. In particular, it focuses on supporting the concurrent execution of the Linux and ERIKA Enterprise OS on the reference platform selected in WP2. Besides the mere concurrent execution of different OSs on the same platform, the task also investigates and designs mechanisms for an efficient synchronization and communication of data between the OSs. As part of this task, several activities have been carried out by the consortium: • The investigation and selection of a suitable hypervisor for the envisioned scenario. • The porting of the selected hypervisor onto the reference platforms. • The design and implementation of the cache colouring mechanism (resulting from Task 5.1). • The design and implementation of the co-scheduling mechanism (resulting from Task 5.3). • The design and implementation of the memguarding mechanism (resulting from Task 5.3) This document will describe all these parallel activities, providing insights about the implementation and information about using the software. Ref: D4.5 HERCULES: Horizon 2020 project #688860 Page 2 D4.5: Multi-OS Integration and Virtualization Figure 1: Overall software infrastructure. 2 Hypervisor 2.1 Introduction Software running safety-critical tasks must be developed according to certified development processes, and to strict safety standards. This process aims at preventing possible injuries due to misbehaving or faulty software. In the case of automotive Electronic Control Units (ECUs), in particular, the Offene Systeme und deren Schnittstellen für die Elektronik in Kraftfahrzeugen / Vehicle Distributed eXecutive (OSEK/VDX) and the newer AUTomotive Open System ARchitecture (AUTOSAR) standards already established a set of rules and constraints for operating systems design, including memory and timing protection, and stack monitoring. These standards impose the usage of a RTOS implementing a set of well-known scheduling algorithms and techniques. Usually, the size of the RTOS is kept at a bare minimum to reduce the code complexity (hence the number of possible bugs) and the costs of the verification process. In addition to this, there is an ever growing interest from the industry for using the advanced features and potential of modern computing platforms, including networking and graphics subsystems, typically supported by a General-Purpose Operating System (GPOS) like Linux. Finally, there is an increased need to integrate together on the same SoC legacy automotive applications based on such OSEK/VDX or AUTOSAR standards, without radically changing the application source code. A hypervisor solution like the one devised in HERCULES is able to fulfill these three requirements, allowing the coexistence of different operating system, guaranteed real-time behavior and integration of legacy applications. In particular, the HERCULES project has chosen to implement a Multi-OS paradigm in which the Linux GPOS and the ERIKA Enterprise RTOS are executed concurrently under the supervision of a hypervisor for proper isolation of the safety-critical activities. The overall infrastructure is the one illustrated in Figure 1. 2.2 Hypervisor Selection Several interesting open-source technologies were available to be used as the basic brick for the hypervisor to be developed in HERCULES. Among the most interesting and actively maintained projects, we can cite: • Jailhouse [KSa18] Ref: D4.5 HERCULES: Horizon 2020 project #688860 Page 3 D4.5: Multi-OS Integration and Virtualization • KVM [KVM; Wik; Red] • Xen [Xen] • Xvisor [Xvia; Xvib] When selecting the most suitable hypervisor for HERCULES project’s scope, we focused on the following re- quirements: • Support for the reference hardware; i.e. ARM. • Real-time capabilities and, especially, the possibility of handling low-latency control). • Availability of the source code under some kind of open-source license (e.g. BSD license, GNU General Public License (GNU GPL), MIT licence). • Good project activity by the development and maintaining community. • Small codebase, which paves the way to a possible certification. These requirements have allowed to narrow the investigation, and eventually to choose Jailhouse. 2.3 Jailhouse Jailhouse [KSa18; Lin] is a project aiming at creating a small and lightweight hypervisor targeting industrial- grade applications. Despite its youth (born in 2013), the project is sponsored by a big company (i.e. Siemens), it received support into the official Linux kernel, and it is getting visibility and traction in the open-source community. The hypervisor supports both the x86-64 architecture, employed by both Intel and AMD, and the 32-bit and 64-bit variants of ARM architectures, provided that the instruction
Load more

Recommended publications
  • Efficient Scheduling Library for Freertos
    DEGREE PROJECT IN INFORMATION AND COMMUNICATION TECHNOLOGY, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2016 Efficient Scheduling Library for FreeRTOS ROBIN KASE KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF INFORMATION AND COMMUNICATION TECHNOLOGY Efficient Scheduling Library for FreeRTOS ROBIN KASE Master’s Thesis at KTH Information and Communication Technology Supervisor: Kenji Kise (Tokyo Institute of Technology) Examiner: Johnny Öberg (KTH) TRITA-ICT-EX-2016:166 Abstract At present, there is a gap between practical implementations of task scheduling on numerous popular Real-Time Operating Systems (RTOSs) and theoretical real-time scheduling. It is difficult to choose what theoretical real-time scheduling concepts to implement when designing a kernel, as theoretical concepts grow and improve over time. Furthermore, the kernel can be kept simpler when offering only simple fixed priority scheduling policy, as advanced scheduling features often require more com- plex implementation and larger overhead. By offering a real-time scheduling library implemented in user space, the user can choose whether to skip the overhead, or use more advanced theories. At the moment there exists already several scheduling frameworks for FreeRTOS. However, they are either difficult to use, not completely implemented in user space, or not providing various theoretical scheduling policies. An open source scheduling library for FreeRTOS implemented in user space that is user friendly and runs with low overhead, Efficient Scheduling Library (ESFree) is proposed. The proposed scheduling library provides polling server that runs aperiodic and sporadic jobs, dependable timing error detection and handling, Rate-Monotonic Scheduling (RMS), Deadline-Monotonic Scheduling (DMS) and Earliest Deadline First (EDF) scheduling policies to provide theoretical real-time scheduling features to speed up development of complex projects, and make FreeRTOS friendlier to students who have newly studied real-time scheduling.
    [Show full text]
  • Download The
    ERIKA Enterprise Current limitations and possible solutions Version: 7 February 11, 2016 DRAFT About Evidence S.r.l. Evidence is a company operating in the field of software for embedded real-time systems. It started in 2002 as a spin-off company of the Real-Time Systems (ReTiS) Lab of the Scuola Superiore Sant'Anna (Pisa, Italy). Today, Evidence is a dynamic company having collaborations in the field of electronics, telecommunications, automotives, and industrial automation. People at Evidence are experts in the domain of embedded and real-time systems, with a deep knowledge on the design and specification flow of embedded software, especially for the embedded market. Besides providing consultancy services, Evidence also provides: BSPs based on Linux for embedded devices, evaluation boards featuring most innovative 8, 16 and 32-bit microcontrollers for the embedded market, development tools for making embedded software development easier, and tools for the schedulability analysis of real-time tasks running on your final product. For more information see: http://www.evidence.eu.com Contact Info Evidence Srl, Via Carducci 56 Localit`aGhezzano 56010 S.Giuliano Terme PISA Italy Tel: +39 050 99 11 224 Fax: +39 050 99 10 812 For more information about Evidence products, please send an e-mail to the follow- ing address: [email protected]. Other information about the Evidence product line can be found at the Evidence web site at: http://www.evidence.eu.com. This document is Copyright 2011-2015 Evidence S.r.l. Information and images contained within this document are copyright and the property of Evidence S.r.l.
    [Show full text]
  • A Fully Open-Source Platform for Automotive Systems
    A fully Open-Source Platform for Automotive Systems Implementation by Paolo Gai, CEO Evidence Srl Bruno Morelli, Evidence Srl 2 The company Founded in 2002, we do custom design and development of software for small embedded devices ~20 qualified people with an average age of 34 years, 30% PhD Experience in automotive, industrial, white goods RTOS and MCU skills • OSEK/VDX, AUTOSAR, • Automatic code generation Embedded Linux skills • 8 Yrs experience in custom BSPs, U-Boot, kernel drivers, • Initial developers of the SCHED_DEADLINE patch 3 Everything in one slide • We created a completely Open-source solution for Automotive systems + • Linux for HMI, communication and logging • ERIKA Enterprise for real-time performance and control • We will show a demo on a dual core Freescale iMX6 • http://erika.tuxfamily.org • Free RTOS for automotive devices • Open-source license , static linking of closed source code • ERIKA Enterprise is the first and only OSEK/VDX certified open-source RTOS 4 Agenda • IVI system requirements and multicore devices • Main features of Erika Enterprise • Success stories • Towards a fully integrated Open-Source solution with Linux and Erika Enterprise • (some) implementation details • Demo on Freescale iMX6 5 Main Requirements of future IVI systems • Fast Boot • there must be a subsystem ready to go in a few ms • Linux boot times are usually in the order of seconds • Real-Time support • there must be a subsystem with real-time performance • e.g. CAN Bus, motor control • Quality of Service • IVI applications need soft-realtime
    [Show full text]
  • ERIKA Enterprise Basic Manual
    ERIKA Enterprise Basic Manual ...multithreading on a thumb! version: 1.1.2 July 18, 2008 About Evidence S.r.l. Evidence is a spin-off company of the ReTiS Lab of the Scuola Superiore S. Anna, Pisa, Italy. We are experts in the domain of embedded and real-time systems with a deep knowledge of the design and specification of embedded SW. We keep providing signifi- cant advances in the state of the art of real-time analysis and multiprocessor scheduling. Our methodologies and tools aim at bringing innovative solutions for next-generation embedded systems architectures and designs, such as multiprocessor-on-a-chip, recon- figurable hardware, dynamic scheduling and much more! Contact Info Address: Evidence Srl, c/o Incubatore Pont-Tech Viale Rinaldo Piaggio, 32 56025 Pontedera (PI), Italy Tel: +39 0587 274 823 Fax: +39 0587 291 904 For more information on Evidence Products, please send an e-mail to the following address: [email protected]. Other informations about the Evidence product line can be found at the Evidence web site at: http://www.evidence.eu.com. This document is Copyright 2005-2008 Evidence S.r.l. Information and images contained within this document are copyright and the property of Evidence S.r.l. All trademarks are hereby acknowledged to be the properties of their respective owners. The information, text and graphics contained in this document are provided for information purposes only by Evidence S.r.l. Evidence S.r.l. does not warrant the accuracy, or completeness of the information, text, and other items contained in this document.
    [Show full text]
  • Embedded Operating Systems
    7 Embedded Operating Systems Claudio Scordino1, Errico Guidieri1, Bruno Morelli1, Andrea Marongiu2,3, Giuseppe Tagliavini3 and Paolo Gai1 1Evidence SRL, Italy 2Swiss Federal Institute of Technology in Zurich (ETHZ), Switzerland 3University of Bologna, Italy In this chapter, we will provide a description of existing open-source operating systems (OSs) which have been analyzed with the objective of providing a porting for the reference architecture described in Chapter 2. Among the various possibilities, the ERIKA Enterprise RTOS (Real-Time Operating System) and Linux with preemption patches have been selected. A description of the porting effort on the reference architecture has also been provided. 7.1 Introduction In the past, OSs for high-performance computing (HPC) were based on custom-tailored solutions to fully exploit all performance opportunities of supercomputers. Nowadays, instead, HPC systems are being moved away from in-house OSs to more generic OS solutions like Linux. Such a trend can be observed in the TOP500 list [1] that includes the 500 most powerful supercomputers in the world, in which Linux dominates the competition. In fact, in around 20 years, Linux has been capable of conquering all the TOP500 list from scratch (for the first time in November 2017). Each manufacturer, however, still implements specific changes to the Linux OS to better exploit specific computer hardware features. This is especially true in the case of computing nodes in which lightweight kernels are used to speed up the computation. 173 174 Embedded Operating Systems Figure 7.1 Number of Linux-based supercomputers in the TOP500 list. Linux is a full-featured OS, originally designed to be used in server or desktop environments.
    [Show full text]
  • Wireless Sensor Network (WSN)
    Catherine Greene Chloe Norris CREU 2010-2011 Wireless Sensor Network (WSN) Detects Uses Temperature Industrial process & Sound monitoring Vibrations Machine monitoring Pressure Monitoring the Motion environment Pollutants Healthcare Home automation Traffic control Source: http://en.wikipedia.org/wiki/Wireless_sensor_network Nodes What it consists of Prices Can have more than one Varies sensor Size Usually has a radio Complexity transceiver A more complex sensor For wireless could be a few hundred communication A less intricate one Small microcontroller could be fairly cheap Energy source Ex: battery Source: http://en.wikipedia.org/wiki/Wireless_sensor_network How they work Sensors support a multi-hop routing algorithm nodes function as forwarders Relay data packets to a base station (known as a wireless ad-hoc network) Think of a sensor like a computer Source: http://en.wikipedia.org/wiki/Wireless_sensor_network Applications Area Monitoring WSN would be put in an area where something is being monitored Ex: a country at war with another may place nodes over a battlefield to detect enemy intrusion, sensors would detect heat, pressure, sound, light, electro-magnetic fields, vibrations, etc… If a sensor went off it would report it to a base station (message might be sent through internet or satellite) Ex: detecting vehicles Source: http://en.wikipedia.org/wiki/Wireless_sensor_network Applications Environmental Monitoring Similar to area monitoring Ex (pictured): state of permafrost in the Swiss Alps
    [Show full text]
  • Paralel Gerçek Zamanli Kiyaslama Uygulama Takimi
    T.C. SAKARYA ÜNİVERSİTESİ FEN BİLİMLERİ ENSTİTÜSÜ PARALEL GERÇEK ZAMANLI KIYASLAMA UYGULAMA TAKIMI YÜKSEK LİSANS TEZİ Sevil SERTTAŞ Enstitü Anabilim Dalı : BİLGİSAYAR VE BİLİŞİM MÜHENDİSLİĞİ Tez Danışmanı : Dr. Öğr. Üyesi Veysel Harun ŞAHİN Nisan 2019 TEŞEKKÜR Yüksek lisans eğitimim boyunca değerli bilgi ve deneyimlerinden yararlandığım, araştırmanın planlanmasından yazılmasına kadar tüm aşamalarında yardımlarını esirgemeyen değerli danışman hocam Dr. Öğr. Üyesi Veysel Harun ŞAHİN’e teşekkürlerimi sunarım. i İÇİNDEKİLER TEŞEKKÜR ........................................................................................................... i İÇİNDEKİLER ...................................................................................................... ii SİMGELER VE KISALTMALAR LİSTESİ ....................................................... iv ŞEKİLLER LİSTESİ ............................................................................................. v TABLOLAR LİSTESİ ........................................................................................... vi ÖZET ..................................................................................................................... vii SUMMARY ........................................................................................................... viii BÖLÜM 1. GİRİŞ …………………………………………………………….................................... 1 BÖLÜM 2. WCET .................................................................................................................... 3 BÖLÜM 3. KIYASLAMA UYGULAMALARI
    [Show full text]
  • COMPARATIVE ANALYSIS of DIFFERENT OPERATING SYSTEMS USED for LOW-END IOT DEVICES 1ZURABIA RIAZ 1University of Management and Technology, Lahore, Pakistan
    VFAST Transactions on Software Engineering http://vfast.org/journals/index.php/VTSE@ 2020 ISSN(e): 2309-3978;ISSN(p): 2411-6246 Volume 8, Number 1, January-December, 2020 pp. 64-72 COMPARATIVE ANALYSIS OF DIFFERENT OPERATING SYSTEMS USED FOR LOW-END IOT DEVICES 1ZURABIA RIAZ 1University of Management and Technology, Lahore, Pakistan. [email protected] Abstract-Internet of Things is the new emerging field projected to interconnect billions of devise through the internet. IoT devices divided into high end as well as low end devices. Linux based operating systems can easily handle IoT based high end devices and due to resource based constraints that includes very less memory, energy power for computation of low end IoT devices makes it difficult to develop. In this paper the main focus is on the detail discussions of the operating systems that will satisfy the requirements of IoT devices for low end categories. Comparative analysis will be performed for different operating system and then the by keeping the focus on the OS which are close to Linux and are fit for the low end IoT devices. Keywords: Internet of Things, Low End Devices, embedded systems 1. Introduction:. Internet of Things or IoT can be root as the availability of excessive and multiple devices (things) interconnected with embedded devices to send and receive data via Internet.For communication different standards for communicating protocols at network layer in-combination with IPv6 has been developed. These protocols as a result enable the heterogeneous devices to connect through internet. In context with hardware, IoT is a collected combination of hardware devices which are heterogeneous in nature.
    [Show full text]
  • Tcc Engenharia Eletrica
    UNIVERSIDADE DO SUL DE SANTA CATARINA MAX BACK SISTEMA EMBARCADO COM RTOS: UMA ABORDAGEM PRÁTICA E VOLTADA A PORTABILIDADE Palhoça 2018 MAX BACK SISTEMA EMBARCADO COM RTOS: UMA ABORDAGEM PRÁTICA E VOLTADA A PORTABILIDADE Trabalho de Conclusão de Curso apresentado ao Curso de Graduação em Engenharia Elétrica com ênfase em Telemática da Universidade do Sul de Santa Catarina como requisito parcial à obtenção do título de Engenheiro Eletricista. Orientador: Prof. Djan de Almeida do Rosário, Esp. Eng. Palhoça 2018 Dedico este trabalho а Deus, por ser o verdadeiro princípio e fim de todas as coisas (das que valem a pena). AGRADECIMENTOS Agradeço a minha esposa Gizele e meus filhos, Eric e Thomas, meus pais e a toda minha família que, com muito carinho е apoio, não mediram esforços para que eu chegasse até esta etapa de minha vida. Agradeço aos professores do curso por terem transmitido seu conhecimento a mim e meus colegas com tanto empenho e dedicação. Não existe triunfo sem perda, não há vitória sem sofrimento, não há liberdade sem sacrifício. (O Senhor dos Anéis – J.R.R. Tolkien, 1954) RESUMO A crescente demanda pelo desenvolvimento de solução conectadas entre sistemas já existentes, assim como a ampliação do uso destes sistemas embarcados mostram a importância de soluções robustas, de tempo real, com ciclos de desenvolvimento cada vez mais curtos e necessidade de reaproveitamento de código. Este trabalho apresenta a seleção do sistema operacional de tempo real FreeRTOS e o experimento de sua utilização como base para o desenvolvimento de um controlador wearable (vestível) em duas plataformas de hardware diferentes, implementando a solução inicialmente em uma delas e depois portando para a outra plataforma, desenvolvendo principalmente a programação específica do novo hardware e procurando manter a parte da aplicação inalterada e independente de plataforma.
    [Show full text]
  • Designing High Throughput Routing Protocol for Wireless Body Area Networks
    International Journal of Technical Research and Applications e-ISSN: 2320-8163, www.ijtra.com Volume 6, Issue 2 (MARCH-APRIL 2018), PP. 85-91 DESIGNING HIGH THROUGHPUT ROUTING PROTOCOL FOR WIRELESS BODY AREA NETWORKS Noor khateeb Ali Khan 1, Shashank Singh 2, Department Of Computer Science Engineering Integral University Lucknow, India Abstract—Wireless Body Area Network (WBAN) is new emerging sub-field of WSN. A key application of Wireless Body A. BAN Positioning Area Network is health monitoring. Wireless sensors are placed BAN is described as a short-range, low-powered device on the human body or implanted in the body to monitor vital that operates around the human body (not limited to humans) signs like blood pressure, body temperature, heart rate, glucose providing a variety of applications. These applications may level etc. Use of Wireless Body Area Network technology to include medical, personal entertainment and consumer monitor health parameters significantly reduces the expenditures electronics. BANs can be described as special WSNs that have of patient in hospital. Wireless Body Area Sensors are used to monitor human health with limited energy resources. Different lesser nodes and much reliable with special importance placed energy efficient routing schemes are used to forward data from on QoS as compared to the tradition WSN. BAN in some cases body sensors to medical server. It is important that sensed data is referred to as BSN. of patient reliably received to medical specialist for further The positioning of BAN in relation with other wireless analysis. To minimize energy consumption and to increase the networks is shown in figure 1.
    [Show full text]
  • ERIKA Enterprise Minimal API Manual
    ERIKA Enterprise Minimal API Manual ...multithreading on a thumb! version: 1.1.3 December 11, 2012 About Evidence S.r.l. Evidence is a spin-off company of the ReTiS Lab of the Scuola Superiore S. Anna, Pisa, Italy. We are experts in the domain of embedded and real-time systems with a deep knowledge of the design and specification of embedded SW. We keep providing signifi- cant advances in the state of the art of real-time analysis and multiprocessor scheduling. Our methodologies and tools aim at bringing innovative solutions for next-generation embedded systems architectures and designs, such as multiprocessor-on-a-chip, recon- figurable hardware, dynamic scheduling and much more! Contact Info Address: Evidence Srl, Via Carducci 56 Localit`aGhezzano 56010 S.Giuliano Terme Pisa - Italy Tel: +39 050 991 1122, +39 050 991 1224 Fax: +39 050 991 0812, +39 050 991 0855 For more information on Evidence Products, please send an e-mail to the following address: [email protected]. Other informations about the Evidence product line can be found at the Evidence web site at: http://www.evidence.eu.com. This document is Copyright 2005-2012 Evidence S.r.l. Information and images contained within this document are copyright and the property of Evidence S.r.l. All trademarks are hereby acknowledged to be the properties of their respective owners. The information, text and graphics contained in this document are provided for information purposes only by Evidence S.r.l. Evidence S.r.l. does not warrant the accuracy, or completeness of the information, text, and other items contained in this document.
    [Show full text]
  • Levels of Specialization in Real-Time Operating Systems
    Levels of Specialization in Real-Time Operating Systems Björn Fiedler, Gerion Entrup, Christian Dietrich, Daniel Lohmann Leibniz Universität Hannover {fiedler, entrup, dietrich, lohmann}@sra.uni-hannover.de Abstract—System software, such as the RTOS, provides no robustness, security and so on; it increases the safety margins or business value on its own. Its utility and sole purpose is to serve makes it possible to cut per-unit-costs by switching to a cheaper an application by fulfilling the software’s functional and nonfunc- hardware. For price-sensitive domains of mass production, such tional requirements as efficiently as possible on the employed as automotive, this is of high importance [8]. hardware. As a consequence, every RTOS today provides some means of (static) specialization and tailoring, which also has a Intuitively, any kind of specialization requires knowledge long tradition in the general field of system software. about the actual application: The more we know, the better However, the achievable depth of specialization, the resulting we can specialize. In the domain of real-time systems (RTSs), benefits, but also the complexity to reach them differ a lot we typically know a lot about our application and its exe- among systems. In the paper, we provide and discuss a taxonomy cution semantics on the employed RTOS: To achieve real- for (increasing) levels of specialization as offered by (real-time) time properties, all resources need to be bounded and are system software today and in the future. We argue that system software should be specialized as far as possible – which is scheduled deterministically. Timing analysis depends on the always more than you think – but also discuss the obstacles that exact specification of inputs and outputs, including their inter- hinder specialization in practice.
    [Show full text]