Fixed-priority scheduling of dual-criticality systems

  • Sanjoy Baruah
  • , Alan Burns

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

15 Scopus citations

Abstract

In modern embedded platforms, safety-critical functionalities that must be certified correct to very high levels of assurance may co-exist with less critical software that is not subject to certification requirements. One seeks to satisfy two, sometimes contradictory, goals upon such mixed-criticality platforms: (i) certify the safety-critical functionalities under very conservative assumptions, and (ii) achieve high resource utilization during run-time, when actual behavior does not live up to the pessimistic assumptions under which certification was made. This paper makes two contributions: (i) it surveys different fixed-priority scheduling algorithms that have been proposed, that seek to balance these two requirements, and (ii) it completes prior work that performs a comparative evaluation of these different fixed-priority scheduling algorithms. It particularly focuses upon the period transformation technique for dual-criticality scheduling, since this technique has received relatively less attention in prior work.

Original languageEnglish
Title of host publicationRTNS 2013 - Proceedings of the 21st International Conference on Real-Time Networks and Systems
Pages173-181
Number of pages9
DOIs
StatePublished - 2013
Event21st International Conference on Real-Time Networks and Systems, RTNS 2013 - Sophia Antipolis, France
Duration: Oct 16 2013Oct 18 2013

Publication series

NameACM International Conference Proceeding Series

Conference

Conference21st International Conference on Real-Time Networks and Systems, RTNS 2013
Country/TerritoryFrance
CitySophia Antipolis
Period10/16/1310/18/13

Keywords

  • fixed priorities
  • mixed criticalities
  • period transformation

Fingerprint

Dive into the research topics of 'Fixed-priority scheduling of dual-criticality systems'. Together they form a unique fingerprint.

Cite this