Electrical Engineering
      and Computer Sciences

Electrical Engineering and Computer Sciences

COLLEGE OF ENGINEERING

UC Berkeley

A Programmable Microkernal for Real-Time Systems

Christoph M. Kirsch, Thomas A. Henzinger and Marco A. A. Sanvido

EECS Department
University of California, Berkeley
Technical Report No. UCB/CSD-03-1250
June 2003

http://www.eecs.berkeley.edu/Pubs/TechRpts/2003/CSD-03-1250.pdf

We present a new software system architecture for the implementation of hard real-time applications. The core of the system is a microkernel whose reactivity (interrupt handling) and proactivity (task scheduling) are fully programmable. The microkernel, which we implemented on a Strong-ARM processor, consists of two interacting virtual machines, a reactive E (Embedded) machine and a proactive S (Scheduling) machine. The system code that runs on the microkernel is partitioned into E and S code. E code manages the interaction of the system with the physical environment: the execution of E code is triggered by environment interrupts, which signal external events such as the arrival of a message or sensor value, and it releases application tasks to the S machine. S code manages the interaction of the system with the processor: the execution of S code is triggered by hardware interrupts, which signal internal events such as the completion of a task or time slice, and it dispatches application tasks to the CPU, possibly preempting a running task. This partition of the system orthogonalizes the two main concerns of real-time implementations: E code refers to environment time and thus defines the reactivity of the system in a hardware- and scheduler-independent fashion; S code refers to CPU time and defines a system scheduler. If both time lines can be reconciled, then the code is called time safe; violations of time safety are handled again in a programmable way, by run-time exceptions. The separation of E code from S code permits the independent programming, verification, optimization, composition, dynamic adaptation, and reuse of both reaction and scheduling mechanisms. Our measurements show that the system overhead is very acceptable, generally in the 0.2 - 0.3% range.


BibTeX citation:

@techreport{Kirsch:CSD-03-1250,
    Author = {Kirsch, Christoph M. and Henzinger, Thomas A. and Sanvido, Marco A. A.},
    Title = {A Programmable Microkernal for Real-Time Systems},
    Institution = {EECS Department, University of California, Berkeley},
    Year = {2003},
    Month = {Jun},
    URL = {http://www.eecs.berkeley.edu/Pubs/TechRpts/2003/5548.html},
    Number = {UCB/CSD-03-1250},
    Abstract = {We present a new software system architecture for the implementation of hard real-time applications. The core of the system is a microkernel whose reactivity (interrupt handling) and proactivity (task scheduling) are fully programmable. The microkernel, which we implemented on a Strong-ARM processor, consists of two interacting virtual machines, a reactive E (Embedded) machine and a proactive S (Scheduling) machine. The system code that runs on the microkernel is partitioned into E and S code. E code manages the interaction of the system with the physical environment: the execution of E code is triggered by environment interrupts, which signal external events such as the arrival of a message or sensor value, and it releases application tasks to the S machine. S code manages the interaction of the system with the processor: the execution of S code is triggered by hardware interrupts, which signal internal events such as the completion of a task or time slice, and it dispatches application tasks to the CPU, possibly preempting a running task. This partition of the system orthogonalizes the two main concerns of real-time implementations: E code refers to environment time and thus defines the reactivity of the system in a hardware- and scheduler-independent fashion; S code refers to CPU time and defines a system scheduler. If both time lines can be reconciled, then the code is called time safe; violations of time safety are handled again in a programmable way, by run-time exceptions. The separation of E code from S code permits the independent programming, verification, optimization, composition, dynamic adaptation, and reuse of both reaction and scheduling mechanisms. Our measurements show that the system overhead is very acceptable, generally in the 0.2 - 0.3% range.}
}

EndNote citation:

%0 Report
%A Kirsch, Christoph M.
%A Henzinger, Thomas A.
%A Sanvido, Marco A. A.
%T A Programmable Microkernal for Real-Time Systems
%I EECS Department, University of California, Berkeley
%D 2003
%@ UCB/CSD-03-1250
%U http://www.eecs.berkeley.edu/Pubs/TechRpts/2003/5548.html
%F Kirsch:CSD-03-1250